Claude Code tiered routines: Opus designs, Haiku sweeps, Sonnet fixes
Opus 5.5 authors scheduled routines, Haiku 5.5 runs high-frequency background sweeps, Sonnet 5.5 patches code, and Jev routes the micro-forks that need no thinker.
THIS IS AN ACTUAL F*CKING GOLDMINE Anthropic just shared one of the best tricks for Claude Code The idea: let Opus 5.5 design your scheduled routines, and swarm the new Haiku 5.5 in parallel 24/7 while your laptop is closed Continuous background engineering with zero Opus burn: cloud tasks run non-stop and Opus only reviews the final diffs You just launch Claude Code like this: claude --model sonnet /schedule here's the split: → Opus 5.5 designs routine workflows: audits cloud task permissions and reviews automated PRs before sign-off → Sonnet 5.5 executes code fixes: investigates build failures and patches code only when a scheduled run catches a regression → Haiku 5.5 runs background sweeps: executes high-frequency polling, dependency checks, and cron routines at 340 tok/s → you stop burning Opus context on routine 24/7 monitoring and keep your token bill razor thin Opus only steps in at three moments: → authoring the cloud routine before the run → reading verified findings after the sweep finishes → signing off on automated PRs before anything ships to git Opus designs · Haiku sweeps · Sonnet fixes JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split the full tree > Opus 5.5 configures cloud routines and audits organization permissions > Haiku 5.5 executes recurring scheduled sweeps at 340 tok/s > Sonnet 5.5 patches code and cuts PRs when a scheduled run catches an issue > Cloud tasks run 24/7 on Anthropic infrastructure with zero machine uptime needed > /loop polls active PRs and CI checks right inside your terminal session > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Configure recurring background audits and dependency checks as Cloud Scheduled Tasks using /schedule 2. Delegate all high-frequency polling and routine interval sweeps to Haiku 5.5 at 340 tok/s 3. Spawn Sonnet 5.5 to investigate failures, patch code, and submit PRs only when a scheduled run flags an issue 4. Use session-scoped /loop for active CI monitoring and interactive PR verification 5. Reserve Opus 5.5 for routine architecture review and final sign-off before merging Show me every change as a diff first. No edits until I say go" ↳ http://code.claude.com/docs/en/scheduled-tasks bookmark this, it runs while you sleep
This post quotes another post: x.com/mirku21/status/2098836008468992471