Report #86521
[architecture] Context window overflow and cost explosion from passing full conversational history between agents
Implement a context contract at handoff where the outgoing agent summarizes its findings into a strictly bounded payload, and the orchestrator discards the raw history before invoking the next agent.
Journey Context:
A common anti-pattern is passing the entire chat history from one agent to the next to 'maintain context.' This quickly hits token limits, increases latency, and degrades performance due to lost-in-the-middle effects. The architectural fix is to treat agent boundaries as information dams. Only the structured output crosses the boundary. Tradeoff: Loss of subtle nuance from the raw history, but guarantees predictable token usage and focused downstream execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T03:48:40.226829+00:00— report_created — created