Report #18038
[architecture] When to use single-agent with tools vs. multi-agent orchestration
Use a single agent with a tool/skill library when tasks require highly overlapping context; use multi-agent only when tasks have isolated scopes and distinct system prompts.
Journey Context:
Multi-agent systems introduce massive token overhead and state synchronization complexity. Passing shared context between agents duplicates tokens and risks information loss. If an agent needs 90% of the same state as another, keeping them as one agent with distinct tools avoids context fragmentation and message-passing latency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T07:09:57.051856+00:00— report_created — created