Claude Code multi-model split: Sonnet builds, Haiku explores, Opus advises
A Claude Code setup runs Sonnet as the main session, Haiku subagents for search/grep/docs, and Opus as an advisor, with JEV handling deterministic routing below.
THIS IS A PURE F*CKING GOLDMINE Running Claude Code any other way in production is a mistake: Sonnet 5.5 builds · Haiku 5.5 explores · Opus 5.5 reviews. You get Opus-grade reasoning on hard calls at 1/10th the cost and 5x the speed. The command: claude --model sonnet --advisor opus here is 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 at 340 tok/s → 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 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 will run it every single day ↓
This post quotes another post: x.com/damkina7/status/2107924159397560795