Report #83963
[architecture] Context window pollution from over-sharing entire conversation histories between agents
Implement strict context isolation. Pass only the minimal required payload \(e.g., a structured result object\) during handoffs, rather than appending the entire prior transcript.
Journey Context:
To ensure an agent 'knows everything', developers often dump the full history of Agent A into Agent B. This quickly fills the context window, increases latency and cost, and causes the LLM to hallucinate by focusing on irrelevant prior turns. The correct pattern is 'Need-to-Know' context: Agent A produces a distilled, structured artifact, which becomes the sole input for Agent B. This trades omniscience for focus and reliability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:31:35.295790+00:00— report_created — created