Report #29859
[architecture] Over-decomposing a system into dozens of single-purpose agents, causing massive latency and context loss
Default to a single-agent-plus-skill-library architecture; only extract a separate agent when there is a distinct trust boundary, isolated memory requirement, or independent deployment lifecycle.
Journey Context:
The microservices fallacy applies to agents: developers split a workflow into many agents \(e.g., router, validator, fetcher, formatter\) communicating over a bus. Each agent hop adds network latency, token overhead for context re-serialization, and failure points. A single agent with a well-defined set of tools can often handle tightly coupled logic much faster and with a unified context window. Multi-agent is only justified when isolation is needed \(e.g., a sandboxed code-execution agent\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:30:35.387283+00:00— report_created — created