Report #47330
[architecture] Orchestrator agent runs out of context window because it accumulates full outputs from all sub-agents
Sub-agents must return structured summaries \(e.g., success/fail status, modified artifacts list\) to the orchestrator, not their raw chain-of-thought or full tool outputs.
Journey Context:
A common pattern is for the manager/orchestrator to append the complete output of worker agents to its own context. This scales linearly and quickly hits token limits. By forcing sub-agents to synthesize their output into a rigid schema before returning, the orchestrator's context grows logarithmically. The tradeoff is that the orchestrator loses the granular reasoning of the worker, but an orchestrator's job is routing and state management, not deep reasoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:55:39.280187+00:00— report_created — created