Claude Code multi-model setup: Sonnet codes, Haiku searches, Opus advises
A Claude Code configuration runs Sonnet 5.5 as the main coder, Haiku 5.5 for parallel repo search and docs, and Opus 5.5 only at key checkpoints, with Jev handling deterministic routing branches.
THIS IS ACTUAL F*CKING GOLD Anthropic just quietly dropped one of the best setups for Claude Code The rule: orchestrate Sonnet, Haiku and Opus 5.5 simultaneously, locking every model into the exact lane it dominates Opus-grade intelligence on critical architectural calls, zero Opus burn on routine terminal iterations Launch Claude Code with this flag pair: claude --model sonnet --advisor opus how the workload divides: → Sonnet 5.5 leads the main session and cuts the actual code → Haiku 5.5 swarms repos, greps call sites, and parses docs concurrently → Opus 5.5 remains on standby as advisor for high-leverage checkpoints → you eliminate token waste on work that never required frontier reasoning Opus only gets triggered on three specific events: → right before locking an architectural plan → the second an identical error hits twice → right before marking a complex task complete Sonnet builds · Haiku explores · Opus reviews JEV engineering applies the exact same logic one layer deeper: deterministic branches (file selection, tool dispatch, fast retry vs abort) clear in sub-milliseconds, so the frontier models only handle genuine forks the architecture tree: > Sonnet 5.5 drives the primary terminal session and edits code > search crawls repo structure on Haiku 5.5 > grep locates call signatures on Haiku 5.5 > docs fetches API specs and schemas on Haiku 5.5 > Opus 5.5 stands on call as advisor, ingesting full context when pinged > JEV resolves instant deterministic routing feed this tree and prompt directly into Claude Code ↓ "Configure my Claude Code environment around this multi-model tree: 1. Run the primary session on Sonnet 5.5 with Opus 5.5 as advisor 2. Spawn three read-only Haiku 5.5 subagents: search (repo mapping), grep (call sites), docs (API references) 3. Enforce one rule in CLAUDE.md: ping advisor before locking any plan, upon repeating any error twice, and before final task handoff 4. Route instantaneous deterministic forks (tool choice, path check, retries) through JEV Show every file update as a diff first, make zero changes without confirmation" ↳ http://code.claude.com/docs/en/advisor bookmark this, you'll run it every single day
This post quotes another post: x.com/damkina7/status/2107924159397560795