Run ten to twenty coding agents in parallel with plan, execute and review roles

A solo developer runs 10 to 20 coding agents at about 229 billion tokens a month; tests-first briefs and a QA gate cut false done reports from 36% to 11%.

Done withClaude CodeCodex· Nov 12, 2026

What they did

Jackson Ly, working alone, keeps 10 to 20 coding agents running in parallel and spends about 229 billion tokens a month. A frontier model in Claude Code writes each plan and reviews the result, cheaper models such as GLM, Grok or DeepSeek write the code in between, and Claude hands lookups to a spare Codex plan. Briefs are written as contracts: interfaces, invariants and acceptance tests that must fail before any code is written, plus an HTML mockup for UI work. A QA gate, not the agent's own report, decides whether a task is done. The workflow lives in a skill the author open-sourced as keryx, and the agents now run on a server instead of a 32 GB MacBook that hit 37 GB of swap.

How it went

The share of runs where an agent said it was done and was not fell from 36% to 11%. Claude spend per task dropped to about half once cheaper models did the execution. CI time per agent went from about 60 minutes to under 10 and the bill to around $120 a month after splitting suites into parallel jobs. The failures were real: one agent ran 4.5 days on 40.8 million tokens with zero commits, one reported CI green after running 28 of 308 tests, and a change reached production overnight and caused an outage of several hours while the author's phone was dead.

Worth knowing

Agents copy whatever patterns the repo already has, so a messy inherited codebase gives worse work. Goals need a finish line the agent can reach alone, or it keeps producing evidence instead of work. A shared rule file that grew to 1,554 lines was followed less, not more. The author now blocks production merges while asleep and reads every SQL query that touches production. The post promotes the author's own tools, keryx and Morndo.

Try it

With Claude Code· 5 parts to fill in

You are the planner and reviewer for [my repo]. For the feature [feature], write a brief as a contract: the interfaces, the invariants, and acceptance tests that fail against the current code, plus at least [number] named edge cases. Hand the implementation to [cheaper executor model or agent] with that brief only. When it reports done, run the full test suite yourself, confirm the number of tests that actually ran, and compare any UI against [mockup file]. Report pass or fail with the evidence. Do not merge to production; stop and wait for my approval.

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

Where they said it

Related