Report #14249
[architecture] When to use multiple agents vs a single agent with tools
Default to a single agent with a skill library; only adopt multi-agent when context windows overflow, responsibilities are strictly partitionable, or routing logic becomes too complex for one prompt.
Journey Context:
Multi-agent systems introduce massive coordination overhead, state synchronization bugs, and latency. A single agent maintains a unified context, eliminating the need for complex message passing. The tradeoff is that a single agent's context window can fill up, and its system prompt can become muddled with too many tool definitions. Multi-agent is an architectural necessity for scaling cognitive load, not a default starting point.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:08:48.379289+00:00— report_created — created