Compare vs a CLAUDE.md file
A CLAUDE.md file is a guess you write once.
It is you, at a single moment, trying to predict everything your agent will ever need to know. One file, written by hand, and stale the day after you save it.
A CLAUDE.md file
Oynix
Who writes it
You do, by hand, and you keep writing it.
It forms itself from the work your team already does.
How current
As current as the last time someone remembered to edit it.
Updated as code, tickets and threads change.
What it covers
Only what you thought to include.
Every symbol, decision and conversation, across every repo.
Cross-source
One file. No link to Slack, Jira or Confluence.
Code linked to the tickets and threads that explain it.
The why
Only what you wrote down.
The rationale, traced to where it was decided.
At scale
Unreadable past a few hundred lines.
A graph the agent walks, not a file it re-reads.
Where a CLAUDE.md file still wins
It is instant and needs nothing. For a weekend project, or five conventions that never change, it is exactly the right amount of effort. Oynix is for the point where one file stops being enough.
Keep the CLAUDE.md for the five rules that never change. Let Oynix remember the ten thousand that do.
Other comparisons