Report #71275
[architecture] When to use multiple agents vs a single agent with tools
Default to a single agent with a tool/skill library. Only introduce multiple agents when context windows overflow, distinct system prompts are required for conflicting instructions, or true parallel execution is needed.
Journey Context:
The 'more agents = better' fallacy ignores the quadratic cost of inter-agent communication, context passing loss, and routing failures. A single agent maintains unified context and avoids coordination overhead. Multi-agent should be a scaling strategy, not a starting architecture.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:12:38.476583+00:00— report_created — created