ZeroTwo reads project instruction files before doing Work or ZeroCode work in a local folder. Use them to set repository norms, test commands, and working agreements so every run starts with the same context.
Which file ZeroTwo uses
In a local project folder, ZeroTwo loads exactly one instruction file, chosen by priority:
ZEROTWO.md
AGENTS.md
CLAUDE.md
The first file that exists at the project root with non-empty content wins. Lower-priority files are ignored — they do not merge.
Instruction files can include other markdown with @include paths. Content is capped for prompt size; very large files are truncated.
You can also keep global defaults under ~/.zerotwo/ for preferences that apply across projects.
Create project instructions
- In your repository root, add
AGENTS.md (or ZEROTWO.md if you want ZeroTwo-specific guidance to win over other tools’ files):
- Open the folder in the ZeroTwo desktop app (Work or ZeroCode).
- Start a task and ask ZeroTwo what instructions it loaded to confirm the file is active.
Global guidance
Create reusable defaults in your ZeroTwo home directory:
Project-root ZEROTWO.md / AGENTS.md / CLAUDE.md still take precedence for that folder when present.
What to put in instruction files
Good instruction content is short, actionable, and stable:
- Build, lint, and test commands for the repo
- Style or architecture constraints
- Files or directories to avoid
- How to open PRs or name branches
- Links to deeper docs the agent should read when needed
Avoid pasting large API references or generated docs into AGENTS.md. Point ZeroTwo at those files instead.
Last modified on August 30, 2026