Switching the coder between projects
A real problem: how the agent knows which project it's in and doesn't mix context.
The problem
The coder agent works on several projects. Without context management it starts mixing stacks, branches and tasks: "which project am I in?".
Why it happens
The agent has one context for all projects. Without explicit switching it blends instructions from different repos.
Solution: an explicit "active project"
1. Keep an 'ACTIVE_PROJECT' file in the working folder with the current project name.
2. Tell the agent: "before every task read 'ACTIVE_PROJECT' and work in that folder".
3. Switching is one command: "switch to 'payments-service'".
What it looks like
- You: "switch to payments-service"
- The agent updates 'ACTIVE_PROJECT', reads the project README, confirms: "Working in payments-service, branch fix/billing".
What else helps
- Separate folders '~/projects/<name>' — a hard boundary.
- Per-project instructions — an 'AGENT.md' in the repo root with stack and rules.
- Explicit task start — "task: fix bug X in payments-service".
Status
Today this is a manual convention (SOUL + 'ACTIVE_PROJECT'). The Roadmap includes automatic project detection from files and per-project persistent memory.