Claude Code setup: Sonnet runs, Jev routes micro-forks, Opus on call
Sonnet 5.5 runs the main session and writes code, three Haiku subagents handle search, grep and docs, Jev resolves thousands of deterministic micro-forks underneath, and Opus is only called on a repeated error or before done.
F*CK RUNNING OPUS ON EVERY TURN Anthropic just showed the cleanest Claude Code advisor setup. Sonnet 5.5 builds everything. Opus 5.5 sits on call and only wakes up when shit actually breaks. Sonnet runs the main session, edits, and runs tests. Three Haiku 5.5 subagents do the dirty work: → search maps the repo → grep finds call sites → docs pulls the API refs JEV sits underneath and resolves thousands of micro-forks (which file, which tool, retry or stop) before anything reaches Sonnet. Opus only gets called twice: → before a plan (reads the whole session) → when the same error hits twice It never writes code itself. It just looks at the full transcript and says “wrong fixture, not the code.” Sonnet applies the advice. Zero regressions. Contract clean. All green. You launch it like this: claude --model sonnet --advisor opus The full tree > Sonnet 5.5 runs the main session and writes code > Haiku 5.5 x3 - search / grep / docs > JEV routes deterministic forks > Opus 5.5 on call - only on same error x2 or before done > Sonnet applies the advice and verifies 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 and --advisor opus. Delegate search, grep, and docs to Haiku 5.5 subagents. Route deterministic forks (which file, which tool, retry or stop) through JEV. Only call Opus when the same error hits twice or before done. Opus reads the full session transcript and gives advice. Never writes code itself. Sonnet applies the advice, shows the diff, then verifies. Show me every change as a diff first. No edits until I say go. save it, it’ll come in handy.
This post quotes another post: x.com/mirku21/status/2098836008468992471