Claude Code multi-model workflow with optional Jev routing
Opus plans, Haiku scans read-only, Sonnet patches and a separate verifier checks results, with orchestration in a reusable script; Jev is optional for routing decisions that don't need heavy reasoning.
this claude code setup is a f*cking goldmine stop making your most expensive model babysit every file in the repo give it the architecture let cheaper agents handle the repetitive work the setup: → opus writes the workflow → haiku handles read-only scans → sonnet handles fixes → a separate verifier checks the results that model split is the configuration to ask for, not something to assume is already enabled the important part is where the loop lives instead of dumping every worker conversation into the main chat, put the orchestration in a reusable script the script coordinates the work opus gets the findings that actually need its attention start with: claude --model opus --effort ultracode then describe the task and the model split you want for a repo-wide cleanup, i'd structure it like this: 1. scan a small directory first 2. collect findings with file paths and evidence 3. reject duplicates and unsupported claims 4. give each editor an isolated worktree 5. verify the patches independently 6. bring the surviving results back for review opus plans haiku searches sonnet patches and none of them gets to approve its own homework the JEV layer is optional: if you already have it wired in, use it for the routing decisions that don't need another heavyweight reasoning call paste this into claude code: “Design a reusable workflow for this repository. Use Opus for planning and final review, Haiku for read-only discovery, and Sonnet for edits where those models are available. Keep editing agents in separate worktrees. Require evidence for every finding and an independent verification pass for every proposed fix. Stop fix loops after two rounds without progress. Start with one directory so we can inspect quality and usage before scaling up. Show the workflow and proposed configuration changes first. Do not edit files or commit anything until I approve.” one catch: parallel agents still consume tokens less clutter in the main context does not mean free compute save the expensive reasoning for decisions that deserve it
This post quotes another post: x.com/sector_sol/status/2093769463065702779