Report #17137
[architecture] Over-decomposing tasks into multiple agents causes context loss and routing overhead
Default to a single agent with a rich skill/tool library; only introduce a second agent when there is a hard context window boundary or a strict isolation requirement.
Journey Context:
The 'crew' metaphor is seductive, but every agent handoff risks dropping context, adds latency, and requires complex routing logic. A single agent with 20 tools maintains a unified world model. Multi-agent is only justified when the context for one task exceeds the LLM's limit, or when security sandboxing demands it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T04:39:40.665997+00:00— report_created — created