Run ten coding agents at once with written briefs and a manager agent

Jackson Ly ran up to ten Claude Code agents at once across a Mac and a home PC and merged 1,029 pull requests in 30 days, using 225 billion tokens.

Done withClaude CodeCodexinGitHub· Oct 18, 2026

What they did

Jackson Ly, working alone, ran Claude Code agents on a Mac and a home PC for 30 days, from 15 September to 14 October, often with ten or more running together and agents working through the night. At first a few agents at once was more than Ly could keep up with. Ly changed the work so it needed less attention: each agent got a written brief and a check for done fixed before it started, kept its state in files and a shared task list, and one manager agent on the PC tracked who was doing what and passed up only the decisions that needed a person. The agents worked across 21 repositories, rebuilding a SaaS product, building an event platform and a directory site, writing tax and legal explainers, and doing most of the QA by design parity checks and golden tests. Ly also ran Codex in goal mode on an open-source project, and later moved worker sessions on the PC to the cheaper GLM-5.3 model.

How it went

Average concurrency went from 2.0 agents to 6.9, and hours with an agent running from 38 to 145 a week. In 30 days Ly merged 1,029 pull requests (406 features, 293 fixes), about three agent-hours each, on 225.1 billion tokens, about $97,000 at list price, though the actual cost was flat plan fees. Almost 98% of tokens were cached context re-reads. One Codex goal run went 4.5 days with zero commits because its stop condition needed a step only Ly could do; after a rewrite the next session made 17 commits. Fresh reviewer agents still corrected 11 of 64, 11 of 44 and 17 of 26 statements in explainers the writers had marked as checked.

Worth knowing

Most of the subagents named no model and so inherited Opus from their parent, even though Ly's rule was to run cheap models for execution. Set a model on every subagent. An overnight usage limit paused 30 agents for four hours; they resumed without loss only because state lived in files. The pull request count includes Ly's own work, and the post was written with AI help.

Try it

With Claude Code· 5 parts to fill in

You are the manager agent for my coding work across [list of repositories]. Keep a shared task board in [path to task file]. For each task, write a brief with the goal, the files in scope and a check for done that is fixed before work starts, then hand it to a worker subagent running on [cheaper model] and record its state in the board. Workers keep their progress in files, not the conversation, so they can resume after a limit or crash. Run at most [number] workers at once. Only bring me decisions that need me: unclear scope, a failing check that needs a judgement call, or anything touching [production or billing]. Stop a worker after three failed attempts at the same step and ask me.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related