Guide
CLAUDE.md, AGENTS.md, GEMINI.md: which tool reads which file
Each coding agent reads its own instruction file, and most can also read AGENTS.md. A repository can keep one shared AGENTS.md and add only what a single tool needs. Personal preferences belong in a separate file in the home folder.
Which file does each tool read?
| Tool | Project file | Personal file | AGENTS.md |
|---|---|---|---|
| Claude Code | CLAUDE.md | ~/.claude/CLAUDE.md | Read if the project has no CLAUDE.md |
| Codex | AGENTS.md | ~/.codex/AGENTS.md | Its own format |
| Cursor | .cursor/rules/*.mdc | User rules in settings | Read |
| Copilot in VS Code | .github/copilot-instructions.md | ~/.copilot/copilot-instructions.md | Read |
| Gemini CLI | GEMINI.md | ~/.gemini/GEMINI.md | Read if set in context.fileName |
Each file has its own guide: CLAUDE.md, AGENTS.md, Cursor rules, Copilot instructions and GEMINI.md.
How can several tools share one file?
Keeping the shared instructions in AGENTS.md reaches most tools without copies. Two of them need one extra step.
Claude Code reads AGENTS.md by itself only when the project has no CLAUDE.md. If it does, a CLAUDE.md that imports the shared file gives Claude both, with room for anything specific to Claude Code:
@AGENTS.md ## Claude Code Use plan mode for changes under src/billing/.
A symbolic link from CLAUDE.md to AGENTS.md also works, but the documentation advises the import when anyone on the project uses Windows, where such links need Administrator rights or Developer Mode.
Gemini CLI needs its file name set in settings.json:
{
"context": {
"fileName": ["AGENTS.md", "GEMINI.md"]
}
}What belongs in the project file, and what in the personal one?
The project file holds what is true of the code for anyone working on it: commands, conventions, files not to touch. It is committed and shared. The personal file holds how you prefer to work, and it follows you into every project without being imposed on your colleagues.
A preference committed to a shared repository becomes everyone's instruction, and a project command kept in a personal file is missing for everyone else.
Why does a file sometimes have no effect?
These files are context for the model, not enforced settings, so the first step is to confirm that the file loaded: /context in Claude Code, /memory show in Gemini CLI. The causes and checks for Claude Code are in the guide on an ignored CLAUDE.md.
Sources, checked on
- Claude Code docs: AGENTS.md and CLAUDE.md
- OpenAI: Custom instructions with AGENTS.md
- Cursor docs: Rules
- VS Code: Custom instructions
- Gemini CLI docs: GEMINI.md files
Where Coredence fits
A shared AGENTS.md solves the project part. The personal files remain separate copies, one per tool, and they drift apart. Coredence builds one record of how you work from your own sessions, commits and notes, and writes it to the personal file of each tool you turn on: ~/.codex/AGENTS.md, ~/.gemini/GEMINI.md and ~/.copilot/copilot-instructions.md, in its own marked section, leaving your own text untouched. Claude Code receives it as a skill.
Coredence runs on macOS 14 or later (Apple silicon) and Windows 10 or later, with no Coredence account. Consolidation needs a model, and you choose it: your Claude Code subscription, your own API key, or a local model through Ollama. On those paths Coredence itself is free to use. It is not open source, and its own paid plans are not on sale yet.
Try it in your browser