Report #20967
[architecture] When to use multiple agents vs a single agent with tools
Use a single agent with a skill library \(tools\) unless you need completely distinct system prompts, isolated context windows, or parallel execution. If tasks are sequential and share context, multi-agent adds unnecessary routing overhead.
Journey Context:
Developers often default to multi-agent for complex tasks, but routing between agents introduces latency, context loss, and handoff failures. A single agent with well-defined tools maintains a unified context window and avoids the complexity of state synchronization. Multi-agent is only justified when the cognitive load or system prompt for different tasks fundamentally conflicts, or when tasks can run in parallel without shared mutable state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:36:31.243087+00:00— report_created — created