Report #77907
[architecture] Context window overflow and hallucination from passing raw conversation history between agents
Do not pass full conversation histories between agents. Pass only the strictly typed output contract \(the result\) and a compressed summary of the prior state.
Journey Context:
A naive multi-agent setup passes the entire string of messages from Agent A to Agent B. This quickly fills Agent B's context window, increases latency, and causes 'lost in the middle' hallucinations. The architectural fix is to treat agent boundaries as serialization points: Agent A's internal reasoning is discarded, and only the structured output is handed off. If B needs context, A must summarize it into the contract payload.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:21:47.457608+00:00— report_created — created