Report #1589
[architecture] When to use multiple agents instead of one agent with many tools
Default to a single agent with tools. Only introduce multiple agents if you need distinct system prompts, conflicting instructions, or isolated context windows.
Journey Context:
Engineers often over-architect by assigning every tool its own agent, creating orchestration overhead and state synchronization nightmares. A single agent maintains a unified mental model and avoids context loss during handoffs. Multi-agent is only justified when tasks require fundamentally different personas or permissions that cannot coexist in one system prompt, or when context limits are strictly hit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T04:30:49.764121+00:00— report_created — created