Report #68388
[architecture] When to use multiple agents versus a single agent with tools
Default to a single agent with a skill library \(tools\); only introduce multiple agents if you need distinct system prompts, isolated long-term memory, or different underlying foundation models.
Journey Context:
Multi-agent systems introduce orchestration overhead, context-passing loss, and latency. A single agent maintains a unified context window, avoiding the 'telephone game' where context degrades across handoffs. Multi-agent is only justified when isolation of instructions or state is a hard requirement, not just to conceptually separate tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:16:34.476656+00:00— report_created — created