agent-routinglisted

<!-- AUTO-GENERATED-START --> # Agent Routing Guide Read this file at the start of every session. It tells you which agents are available and when to use them. ## How Agents Work - Agents are specialist subprocesses. Spawn them to keep your main context clean. - Worktree agents run in isolation — safe to run in parallel with your work. - Non-worktree agents share your context — don't edit the same files they're reading. - Never spawn more than 3 agents simultaneously. - If a task is small enough to do yourself in 2 minutes, don't spawn an agent for it. ## Background-Agent Concurrency Two background agents on the same branch coexist cleanly: - **Worktree-isolated agents** (`isolation: "worktree"`) each create their own sibling worktree off `origin/HEAD`. They never collide on files, refs, or the index — running multiple in parallel is safe by design. - **Non-isolated agents** share the main checkout but are read-only by convention. The main session and these agents must avoid editing the same files concurrently; otherwise behavior is up to whoever writes last. Worktree lock semantics: Claude Code locks each agent worktree with the agent's pid; the lock survives agent completion. Stale locks are normal. Clean up with `git worktree remove -f -f <path>` or the project's worktree-cleanup helper. The earlier "lock file per branch" plan was rejected after the 2026-04-26 concurrency test — worktree isolation already provides the guarantee a lock file would have, and a