Report #1566
[architecture] Over-engineering with multiple agents when a single agent with tools suffices
Default to a single agent with a skill/tool library. Only introduce multiple agents if you need parallel execution, strict context isolation, or completely conflicting system prompts.
Journey Context:
The intuition is that complex tasks need many agents, but LLMs struggle to maintain coherent persona and context when overloaded. Multi-agent systems introduce orchestration overhead, state synchronization latency, and error propagation. A single agent with well-defined tools keeps the full context in one window, avoiding the 'telephone game' of inter-agent communication. Multi-agent is only justified when the cognitive load or context window genuinely exceeds a single agent's capacity, or when security/isolation demands it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T02:32:26.201806+00:00— report_created — created