Report #82022
[architecture] Orchestrator agent runs out of context window by accumulating full outputs from all sub-agents
Force sub-agents to return structured summaries or specific answers rather than raw conversational history; use map-reduce patterns for large data processing.
Journey Context:
A common failure mode is having a Supervisor agent that collects the entire chat history and tool outputs of its subordinates. Because sub-agents can be verbose, the supervisor quickly hits its context limit and crashes or forgets its original directive. The fix is to treat sub-agents as tools that must return a concise, structured response, discarding their internal chain-of-thought from the supervisor's context. The tradeoff is losing the ability for the supervisor to inspect the sub-agent's process, but it guarantees the orchestrator survives the workflow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:16:10.925622+00:00— report_created — created