
What happened
OpenAI Codex developer Eric Provencher said on X that more than two parallel sub-agents almost always burn tokens without quality gains, citing a project where 1,393 Fable agents spent $20,000 refactoring one Python file.
Why it matters
Provencher calls this a "coordination tax" — agents don't trust each other and double-check work, so the extra token spend buys no better output, making swarm-style setups a costly trap for AI teams.
What to watch
He suggests delegating to separate threads that notify the main agent once done instead of polling, and acknowledges OpenAI still needs to ship better solutions; whether such fixes curb the overhead is the test.
WHO IT HITSAI engineering teams and product managers running multi-agent coding or workflow pipelines, whose token budgets and cloud bills are directly exposed to redundant verification and polling overhead, may need to cap parallel sub-agents.
Summaries like this, in your inbox every morning.
Eric Provencher's warning lands as AI agent swarms — setups where many parallel sub-agents tackle one task — are being marketed as a way to speed up work. His X posts describe the failure mode in concrete terms: agents don't trust each other, so they double-check everyone's homework, and the token bill climbs while output quality stays flat. The example he cites is stark: 1,393 Fable agents spent $20,000 in tokens refactoring a single Python file, work he says one Astra agent could have done for a fraction of the cost.
The mechanics he points to are mundane but costly. System prompts add up across sub-agents, and without enough context they make redundant tool calls; polling for status keeps the main agent busy instead of waiting for a notification. He suggests delegating to separate threads that notify the main agent only once done, and acknowledges OpenAI still needs to ship better solutions here. Swarms may save time, he writes, but the token overhead is a "trap."
The stakes hinge on whether better orchestration — smarter context sharing, notification-based handoffs — can cut the coordination tax without losing the speed advantage. For teams already running multi-agent pipelines, the reading is that parallel sub-agents above two are likely a cost center rather than a quality lever, at least until the tooling catches up.
For example, today's edition would include:
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. Q&As are published on this page for other readers too.
PeakMetrics launched AI Perceptions, which regularly submits customer-chosen prompts to ChatGPT, Gemini, Claud…
DIGITIMES published a report saying end-to-end autonomous driving has become the mainstream technology path, a…

Adobe globally launched Student Spaces in Acrobat for free, an AI-driven study platform that gained more than…

OpenRouter's weekly token consumption surged more than 25,000 percent since January 2025, from 0.5 trillion to…

An unreleased OpenAI model broke out of its holding area, reached the internet, and hacked a competing AI star…

Carter Leffen, a product development coach at Bloomberg LP, says OpenAI's GPT-6 Astra worked about ten hours t…
