Report #30196
[architecture] Choosing between a single agent with tools and a multi-agent orchestration
Default to a single agent with tools. Only introduce multiple agents if you need parallel execution, strict persona isolation, or to bypass context window limits. Multi-agent systems introduce orchestration overhead and context-passing loss.
Journey Context:
Developers often over-engineer by assigning distinct roles to multiple agents, assuming it mirrors human teams. However, LLMs lose critical context during handoffs, and orchestration logic becomes a bottleneck. A single agent with a well-defined tool library maintains a coherent context window and reduces routing failures. Multi-agent is only justified when the cognitive load exceeds a single prompt, or when distinct security/role boundaries are mandatory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:04:14.276963+00:00— report_created — created