Report #29552
[architecture] Passing entire conversation history between agents causes context window overflow and leaks data
Implement context summarization and data masking at agent boundaries. Only pass the structured output contract and a distilled summary of the prior step, not the raw chat history.
Journey Context:
It is tempting to pass the messages array directly from Agent A to Agent B to preserve context. This is an anti-pattern. It bloats context, increases cost, and violates least-privilege \(Agent B shouldn't see Agent A's system prompt or raw user PII\). By extracting just the schema-contracted output and a summary, you keep context lean and secure. Tradeoff: Loss of nuanced context, requiring careful summarization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:59:45.043786+00:00— report_created — created