for Claude Code + Codex
Same work. Up to 80% less plan usage.
It's Wednesday and your weekly limit is gone. Not on judgment: on greps, boilerplate, and test files that all ran at your primary model's rate. Conductor keeps your best model for the thinking and routes the labor to cheaper tiers. No magic, just routing.
Backs up everything it touches. Managed markers. One-command undo.
One expensive thinker. Five cheap pairs of hands on this one job.
the problem
Your best model is doing your worst work.
Fable 5 is the best model you can rent and the fastest way to torch a week's plan. Every grep, every boilerplate edit, every test file burns at your primary model's rate. Subagents make it worse: by default they inherit that same expensive model, which is how people lose half a weekly limit in one afternoon. The fix is not a cheaper model. It is the right model for each job.
what actually happens
You don't run Conductor. Your next session becomes it.
-
01
Install once.
One command writes four pinned agents and one managed block into your CLAUDE.md (AGENTS.md on Codex).
-
02
Open a new session.
It reads that block and takes the podium: from your first message it plans on your primary model and hands greps, builds, and reviews to the cheap tiers on its own. Nothing to remember, no new workflow.
-
03
Save /conductor for the big ones.
Hand it a whole objective and it runs the full loop: recon, plan, parallel waves, verification rounds, synthesis. (Codex: $conductor.)
# ...your existing notes, untouched... + <!-- conductor:start --> + Plan on your primary model. + Route greps, builds, and reviews to sonnet and haiku. + <!-- conductor:end --> # ...the rest of your CLAUDE.md, untouched...
how it works
You conduct. Cheaper models play.
-
You conduct.
The session's primary model does only what expensive reasoning is for: intent, decomposition, routing, judgment, synthesis.
-
The crew plays.
Builders write the code, scouts gather facts, critics review, all in parallel, all at crew prices.
-
Your plan stretches.
Weekly limits weight usage by per-token cost, and the labor is the bulk of the tokens. Move the labor down a tier and the same plan does more work.
one conductor, four workers, one verified result
mid tier = sonnet · small tier = haiku · top tier = opus
the crew
Four agents, pinned to a tier.
Features, fixes, refactors, tests, scripts, drafts.
Greps, inventories, config dumps, status checks. Read-only.
Adversarial review panels that try to break the work.
Deep design for epics. Used sparingly.
Every agent's model is pinned in its own config file, so a dispatch can never silently run at your primary's rate. That silent inheritance is exactly how subagent-heavy sessions eat weekly limits.
the fable 5 era
Reserve your primary for the hardest 10%.
You already run the pattern by hand: plan on the expensive model, hand the labor to Sonnet and Haiku, save the top tier for hard problems and review. Conductor is that pattern, installed. Your primary does judgment and synthesis only. The crew does everything else, at crew prices.
the math, honestly
Usually 60-80% less. Sometimes more.
Weekly plan limits (or your API bill) weight usage by per-token cost. On build-heavy work the execution tokens dwarf the orchestration tokens, so routing the labor to cheaper tiers commonly burns 60-80% less, the same fact as stretching a plan up to 5x longer. That range is measured against a top-tier metered primary. Less if your primary is already mid-tier, more if you delegate aggressively. No magic, just routing.
install
One command. Then forget it's there.
Uninstall anytime:
Requirements
-
Claude Code: the
sonnetandhaikutiers (any paid plan).opusonly for the architect. - Codex CLI: GPT-5.4 and GPT-5.4-mini. GPT-5.5 only for the architect.
faq
Ask the annoying questions.
--uninstall removes exactly that block and nothing else. If the markers ever look tampered with, it refuses to guess and tells you instead./model. You will not remember to.Your best model has better things to do.
One command. Every session after this one conducts on its own.