Report #51881
[architecture] Deciding between single-agent-plus-tools vs multi-agent architecture
Default to a single agent with a skill/tool library. Only introduce multiple agents if you require parallel execution, strict state isolation, or fundamentally conflicting system prompts.
Journey Context:
Multi-agent systems are often chosen prematurely due to the 'division of labor' analogy. However, agents cannot share a context window natively. Passing context between agents is lossy, expensive, and introduces massive state synchronization overhead. A single agent with tools retains the full conversational context and avoids handoff failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:34:29.066281+00:00— report_created — created