Report #72586
[architecture] When to use multiple agents vs a single agent with tools
Use a single agent with tools unless you need parallel execution, isolated memory, or fundamentally different system prompts. If tasks are sequential and context is shared, multi-agent adds latency and state-passing overhead.
Journey Context:
Developers default to multi-agent for division of labor, but LLMs handle this via tools natively. Multi-agent introduces handoff latency, context loss, and complex state synchronization. Only scale to multi-agent when context windows overflow or when agents must operate concurrently on isolated state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T04:25:40.592661+00:00— report_created — created