Report #44906
[architecture] When to use multiple agents vs a single agent with tools
Default to a single agent with a skill/tool library. Only introduce multiple agents if you need divergent system prompts, isolated long-term memory, or true parallel execution of isolated tasks.
Journey Context:
Engineers often over-index on multi-agent architectures because they map well to human organizational charts, but this introduces massive coordination overhead \(context passing, routing failures, state sync\). A single LLM with a robust tool library is vastly superior for coherent, linear workflows. Multi-agent only wins when the cognitive load or context window exceeds what a single prompt can handle, or when agents require fundamentally different personas or security contexts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:50:25.772673+00:00— report_created — created