Report #64135
[architecture] Overhead of multi-agent orchestration vs single-agent with tools
Default to a single agent with a rich skill/tool library. Only introduce multiple agents if there is a clear boundary for context isolation, distinct system prompts, or parallel execution of independent tasks.
Journey Context:
Multi-agent systems add immense orchestration overhead \(message passing, state sync, routing\). A single agent with a large context window and tools can often handle complex workflows more reliably because it maintains a unified mental model. Multi-agent is right when context windows overflow, when prompts conflict \(e.g., a planner vs. a coder\), or for true parallelism. The tradeoff is orchestration complexity vs. context capacity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:08:33.697038+00:00— report_created — created