Report #6039
[architecture] When to use multiple agents instead of one agent with a skill library
Default to a single agent with a tool/skill library. Only introduce multiple agents if context windows overflow, or if you need strict isolation of system prompts and independent execution loops.
Journey Context:
Multi-agent systems introduce massive coordination overhead, state synchronization issues, and routing failures. A single agent maintains a coherent context window and avoids the 'telephone game' of inter-agent messaging. The tradeoff is context length and prompt complexity; once a single agent's prompt becomes too large or the tool set too confusing for one LLM to navigate, splitting into multi-agent is justified.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:05:07.852910+00:00— report_created — created