One task. A team of agents. You merge one PR.
Hand a big job to a lead agent: a migration, a refactor, a large feature. It plans the split, starts sub-agents in parallel, each in its own devbox with its own branch and pull request, and brings their work back as one pull request.
Approve the plan
Start the task in plan mode and describe where you want to end up. The lead proposes how to split the work and what depends on what. Nothing starts until you approve it.
Sub-agents run in parallel
Each sub-agent gets its own devbox, branch, and pull request, and can run a different agent or model from the lead. The tree shows every one of them; open any to watch its devbox live.
The lead integrates
Sub-agent pull requests target the lead’s branch. They fix their own CI and rebase as they go, and once checks pass, the lead merges them in one at a time.
You merge one
Everything lands in the lead’s pull request. You review it and merge it into main yourself.
Work too big for one agent
Migrations
Move a codebase to a new API, framework version, or library, a module per sub-agent.
Large features
Split a feature into its backend, frontend, and tests, built in parallel and integrated by the lead.
Sweeping refactors
Renames, stricter types, and dead code removed across hundreds of files, each slice with its own owner.
Test sweeps
A sub-agent per package, each writing the missing tests and fixing what they expose.
Questions about campaigns
How do I start a campaign?
Ask any task to split the work. In plan mode, the lead lays out the split and the dependencies first, and starts nothing until you approve.
How many agents run at once?
Up to your plan’s limit on tasks running at once, the lead included: 3 on Free, 10 on Starter, 25 on Pro, and 50 on Max. Past it, a new sub-agent is refused until a running one finishes.
Can sub-agents use different agents or models?
Yes. The lead can start each sub-agent on Claude Code, Codex, or OpenCode, with its own model and devbox size.
Who merges?
The lead merges each sub-agent’s pull request into its own branch once checks pass. You review the lead’s pull request and merge it into main.
Can a campaign span repositories?
Not yet. A campaign works in one repository, and every sub-agent shares its project and credentials.
What does it cost?
Each sub-agent is its own devbox, billed by the second like any task. The models run on your own plan.
Stop running one agent at a time.
Hand a big job to a lead agent. Start with free credits.