Working with Large Projects

Codebuff works on large repos (we test against VS Code). If it wanders or burns credits, try these.

Start Codebuff in the part of the repo you care about:

cd backend
codebuff

Or set --cwd:

codebuff --cwd backend

This keeps the context tight.

Keep the root AGENTS.md short and use it as a map. Link to the docs for each area, and the agent opens the ones it needs:

## Services

- Auth: see `services/auth-service/README.md`
- Users: see `services/user-service/README.md`
- API gateway: see `services/api-gateway/README.md`

Only the root file is loaded on its own, so a nested AGENTS.md works only if the root file points to it.

When asking for work in a large repo:

• Point to exact paths
• Mention related files up front
• Break large changes into smaller requests
• Use --max when you need Codebuff to load more files

• Trim noise with .codebuffignore and .gitignore
• Start in the most relevant subdirectory
• Split broad refactors into stages
• Let Codebuff handle file discovery instead of pasting long file lists