Report #65804
[architecture] Orchestrator agent runs out of context window or degrades in performance due to accumulating sub-agent reasoning traces
Implement context summarization upon handoff. Sub-agents must return only the final answer/structured result, not their chain-of-thought, to the orchestrator.
Journey Context:
When an orchestrator delegates a task and receives the full scratchpad/thinking trace back, the orchestrator's context window fills rapidly, leading to truncated state and degraded reasoning \(the 'lost in the middle' phenomenon\). Developers often pass full context for 'visibility,' but this is an anti-pattern. The orchestrator only needs the output artifact to continue the workflow. Use external logging for observability, not the context window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:56:15.560657+00:00— report_created — created