When is running multiple agents worth the coordination overhead?
Describe the conditions under which a multi-agent architecture outperforms a single-agent system, and the conditions under which it degrades performance. What is the key structural property of the task that determines which is better?
Multi-agent wins when sub-tasks are parallelisable, isolate context, or need specialists. It hurts when they form a dependency chain, paying coordination tax for zero concurrency gain.
Imagine writing a research report. If three sections can be researched at the same time, you hand each to a different person and finish in a third of the time. That is multi-agent, and it works because the work splits cleanly. Now imagine a report where each section needs the conclusion of the one before it. Handing it to three people does not help, because person two cannot start until person one finishes. You have just added meetings, handoffs, and confusion for no speed gain. One careful person would have done it faster. AI agents are the same. Splitting a task across many agents helps only when the pieces are truly independent. If the pieces depend on each other in a line, one well equipped agent is usually simpler, cheaper, and easier to debug.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
Open with the deciding question of task independence, then give the three win conditions of parallelism, specialisation, and context isolation. Lay out the costs of coordination overhead, error propagation, and debugging surface. Close with the single-agent default and the explicit trigger that justifies escalating to multi-agent.
| Dimension | Single well-equipped agent | Multi-agent system |
|---|---|---|
| Best task shape | Linear dependency chain | Independent, parallelisable sub-tasks |
| Wall-clock latency | Sequential, predictable | Lower only when branches run concurrently |
| Specialisation | One generalist model for all steps | Specialist model per sub-task |
| Context handling | One transcript, can overflow on huge scope | Isolated narrow scope per agent |
| Coordination cost | None beyond the tool loop | Routing, messaging, shared state sync |
| Error behaviour | Single failure point, easy to trace | Per-step rates multiply, harder to trace |
| Debugging | Trace one trajectory | Debug the orchestration layer too |
Real products, models, and research that use this idea.
- Anthropic's multi-agent research system fans out subagents for parallel search, but its own write-up warns the orchestration and token cost only pay off when sub-queries are independent.
- Claude Code runs as one well-equipped agent with file, shell, and search tools rather than a swarm, because coding edits form a tight read then edit then test dependency chain.
- OpenAI's Swarm and the Agents SDK model explicit handoffs, where one agent yields to a specialist mid-run, which fits routing-style tasks but adds debug surface.
- LangGraph supervisor graphs let a coordinator dispatch worker agents, and teams routinely collapse them back to a single node once they find the sub-tasks were actually sequential.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you quantify when the parallelism win outweighs the coordination tax?
QWhy does end to end reliability often drop when you add more agents?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Reaching for multi-agent by default because it sounds sophisticated. Most tasks have a linear dependency chain, where many agents add coordination cost but no concurrency benefit over one strong agent.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.