One set of preferences for Claude Code, Codex and Cursor

• Claude Code reads CLAUDE.md files: one in your home folder for every project, and one in each repository.
• Codex reads AGENTS.md files, in its own home folder and in each repository.
• Cursor reads its project rules, and user rules set in its settings.

Three agents means at least three places for the same preferences, before you count each repository.

You correct Claude Code about how you like commit messages written. You add it to CLAUDE.md. A week later Codex writes them the old way, because its file never got the change. Each copy is right on the day you edit it, and they slowly drift apart.

• Pick one file as the source. Keep your personal preferences in one file and copy it to the others when it changes.
• Separate personal from project rules. Your taste goes in the personal file. The project's conventions go in the repository, where your team sees them too.
• Check the copies when an agent surprises you. A surprise is often a sign that one copy is behind.

Copying works while you remember to do it. It does nothing for the answers you give in the middle of a task, which never reach any of the files.

Varyz keeps one place for your vision, taste, and creative perspective, and each connected agent consults it.

• One source, every agent. Claude Code, Codex and Cursor ask the same Varyz on your computer. A rule you settle while working in one applies in the others.
• Habits and one-offs kept apart. Rules about how you always work follow you everywhere; choices made for one project stay with that project.
• Your files stay yours. Varyz adds one short marked section to CLAUDE.md and AGENTS.md. Everything else you wrote stays as it is, and you keep using those files for team conventions.

See the full comparison: Varyz vs CLAUDE.md, AGENTS.md and Cursor rules. Download local Varyz for free. More guides.