What is the primary coordination cost that multi-agent systems pay that single-agent systems avoid?
Multi-agent systems pay a coordination tax: routing tasks to the right agent, keeping shared state consistent, and message passing between agents, all of which a single sequential agent avoids.
Imagine one chef cooking a whole meal alone. The chef remembers exactly what is in every pot, so nothing gets out of sync. Now imagine a team of chefs sharing one kitchen. Someone has to decide who chops, who fries, and who plates. The chefs must shout updates to each other so nobody salts the soup twice. If one chef mishears another, the dish is ruined. The team can cook faster when tasks are truly independent, but they spend real effort just staying coordinated. Multi-agent systems are the team of chefs. The coordination, deciding who does what, keeping everyone's view of the meal consistent, and passing messages around, is pure overhead that the lone chef never pays.
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.
Name the three coordination costs, explain why a single agent pays none of them, walk through error propagation and how per-step rates compound, contrast orchestrator with peer to peer topologies, and close with the two conditions, real parallelism or specialisation, that justify going multi-agent at all.
Real products, models, and research that use this idea.
- OpenAI's Swarm and the Agents SDK model handoffs explicitly, where one agent yields control to a specialist, making the routing and message-passing cost a first-class concept.
- LangGraph's supervisor pattern centralises routing in a coordinator node that dispatches to worker agents and reconciles their results in a shared typed state graph.
- Anthropic's multi-agent research system uses an orchestrator that spawns sub-agents for parallel search, then synthesises their findings, paying coordination cost only where parallelism is real.
- CrewAI and AutoGen wire role-specialised agents into teams, where every inter-agent message is a logged hop and a potential point where one agent's error propagates to the next.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow does end to end success rate change as you add more agents in a handoff chain, and what does that imply for design?
QWhen would you choose a peer-to-peer topology over an orchestrator or supervisor topology?
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.
Assuming more agents means more capability. The default is the opposite. Coordination adds latency and failure surfaces, so a single agent wins unless the task has genuine parallelism or specialisation.
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.