Report #1354
[architecture] When to use multiple agents vs a single agent with tools
Default to a single agent with a tool library. Only introduce multiple agents if you require parallel execution, strict isolation of system prompts/personas, or divergent context windows.
Journey Context:
Developers often over-engineer with multi-agent systems because it sounds powerful, but inter-agent communication is lossy, routing is brittle, and context handoffs consume tokens. A single agent with a well-defined skill/tool library is faster and more reliable for sequential tasks. Multi-agent only wins when tasks are truly parallelizable or when a single system prompt cannot accommodate the divergent behaviors required \(e.g., a strict coding agent vs. an empathetic HR agent\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T19:33:53.977637+00:00— report_created — created