STOP POLLUTING YOUR F*CKING MAIN BRANCH
Anthropic just dropped the cleanest worktree setup in Claude Code.
Sonnet 5.5 runs the main session.
Everything else builds in isolated worktrees.
Opus 5.5 sits on call and only wakes up when something actually breaks.
Three worktrees run in parallel:
→ wt-auth (Sonnet medium) edits auth fixtures
→ wt-scout (Haiku 340 tok/s) indexes the repo AST
→ wt-api (Sonnet medium) runs pytest in isolation
Git isolation keeps them clean.
Zero index contention.
When a test fails, Opus gets called, spots the mock system clock fixture, and the patch lands inside the worktree.
Then it squashes everything back.
0 regressions.
Main branch stays clean.
You launch it like this:
claude --worktree feat-auth && claude -w feat-scout --model haiku
The full tree
> Sonnet 5.5 high runs the main session coordinator
> worktree router handles git isolation
> Haiku 5.5 parallel worktree scout
> wt-auth / wt-scout / wt-api run isolated
> Opus 5.5 on call - only before plan, error repeats, or before merge
> squash merge back with 0 regressions
Paste the tree + this prompt into Claude Code ↓
Rebuild my Claude Code setup around this tree:
Run the main session on Sonnet 5.5 with effort high.
Build features inside isolated worktrees (wt-auth, wt-scout, wt-api).
Track the repo AST on Haiku 5.5 at 340 tok/s.
Keep Opus 5.5 on call. Only call it before a plan, when an error repeats, or before merge.
Opus never writes code. It reads the worktree specs and gives advice.
Squash the worktrees back only after a pre-flight contract check with zero regressions.
Show me every change as a diff first. No edits until I say go.
save it, it’ll come in handy.