for Claude Code + Codex
Same work. Up to 80% less plan usage.
Right now every grep and every test file burns your most expensive model. Conductor keeps it for judgment and routes the labor to cheaper tiers. Usually 60-80% less burn. No magic, just routing.
Backs up everything it touches. Managed markers. One-command undo. Read the script before you run it.
how it works ↓One expensive thinker. Five cheap pairs of hands.
the problem
Your best model is doing your worst work.
Every grep, every boilerplate edit, every test file runs on your most expensive model and counts against your weekly limit at the highest rate. You are paying top-tier prices to do bottom-tier work. The fix is not a cheaper model. It is the right model for each job. That is what Conductor does.
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 (sonnet) write the code, scouts (haiku) gather facts, critics (sonnet) review, all in parallel.
-
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
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.
Models are pinned per agent, in each agent's config file, on Claude Code and Codex alike. A dispatch can never silently burn your primary model. sonnet / haiku / opus resolve to whatever your plan provides.
what you get
Delegation, built into the session.
Every session delegates by default.
A managed block in your CLAUDE.md, so it is always on, not a thing you have to remember.
/conductor for the big jobs.
The full loop: recon, plan, parallel dispatch, verification rounds, synthesis.
Safe installer.
Backs up everything it touches, idempotent, one-command uninstall. It never clobbers a file without a recoverable backup.
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 3-5x longer. Less if your session default is already a cheap model, more if you delegate aggressively. No magic, just routing.
install
One command. Then forget it's there.
Read the script before you run it.
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 delegates on its own.