Report #65654
[architecture] Over-decomposing workflows into multiple agents causing context fragmentation
Default to a single agent with a tool library; only introduce multiple agents when there are conflicting system prompts or strict resource isolation needs.
Journey Context:
Mapping human org charts to multi-agent systems is a common anti-pattern. LLMs lose critical context when state is serialized and passed between agents. A single agent maintains full conversational context and avoids handoff latency. Multi-agent is only justified when system prompts logically conflict \(e.g., an optimizer vs a critic\) or when tasks must run in parallel.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:41:12.190187+00:00— report_created — created