Report #11508
[architecture] Agents running out of context window or degrading in performance because they receive the entire raw conversation history of other agents
Implement a summarization and schema-extraction boundary. When transferring control, the outgoing agent must output a structured summary \(e.g., current state, completed steps, next steps\) rather than passing the raw token history to the incoming agent.
Journey Context:
A common mistake is to pass the messages array directly from Agent A to Agent B to 'keep them informed.' This scales quadratically in token consumption with each agent hop, quickly hitting context limits and diluting the active signal with noise from other agents' tool calls. By forcing a summarization boundary, you trade perfect information for bounded context and high signal density. Agent B only needs the 'what' and 'why', not the 'how' \(the raw tool outputs\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:36:36.626146+00:00— report_created — created