Report #4064
[architecture] When to use multiple agents vs a single agent with tools
Default to a single agent with a rich tool/skill library. Only introduce multiple agents if you require parallel execution, strict isolation of system prompts, or fundamentally different persona/security contexts.
Journey Context:
Engineers often assume multi-agent systems are inherently more capable because they mimic human teams. However, LLMs suffer from context fragmentation when state is distributed. Multi-agent introduces orchestration overhead, handoff failures, and context-sharing bottlenecks. A single agent maintains a unified context window, leading to more coherent reasoning. Multi-agent is the right call only when the overhead of context isolation is justified by the need for parallel processing or distinct instruction sets.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:45:26.875447+00:00— report_created — created