Override Files & Local Customization

AGENTS.override.md is a same-level file that takes priority over AGENTS.md at that directory. The primary use case: personal overrides that you do not want checked into version control. Add AGENTS.override.md to your .gitignore, and each developer can customize their Codex experience without affecting the team-shared configuration.

Common override patterns include personal model preferences (defaulting to a specific model), custom slash commands that only you use, debug-mode rules that relax constraints during development, and experimental features that are not ready for the team. The override file is also useful for temporary rules — "for this sprint, always include performance benchmarks in test output" — that you do not want permanently in the shared config.

# Personal Overrides (gitignored)

## Model Preferences
- Default to codex-1 for all tasks
- Use o3 with high reasoning for architecture discussions

## Debug Mode
- When I say "debug mode", add verbose logging to every function
- Include stack traces in error messages during development

## Personal Conventions
- I prefer explicit return types on all functions
- Always show the full file path in code comments

1. Create the override Add AGENTS.override.md at the repo root with your personal preferences.
2. Gitignore it Add `AGENTS.override.md` to .gitignore so personal rules stay local.
3. Document the pattern Add a note in the team AGENTS.md: "Personal overrides go in AGENTS.override.md (gitignored)." This teaches new team members the convention.