Working with Large Projects

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

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

cd backend
levelcode

Or set --cwd:

levelcode --cwd backend

This keeps the context tight.

For big trees, keep knowledge close to the code:

• Add knowledge.md files in important subdirectories:

  services/
  auth-service/
      knowledge.md
      src/
  user-service/
      knowledge.md
      src/
  api-gateway/
      knowledge.md
      src/

• Keep each file focused on that area

• Link related files when the areas overlap

• Use the root knowledge.md for cross-cutting notes

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 LevelCode to load more files

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