Report #22666
[architecture] Context window exhaustion and instruction leakage when passing full chat history between agents
Strip conversational history during agent handoffs, passing only the strictly necessary structured output \(the 'contract'\) and a distilled summary, rather than the raw token history.
Journey Context:
When Agent A hands off to Agent B, developers often pass A's entire chat history so B 'has context'. This is fatal: it consumes B's context window, increases latency/cost, and worse, allows A's internal reasoning or tool outputs \(which might contain injection payloads\) to influence B. B should only receive the exact schema payload it needs to do its job. Tradeoff: B loses nuance from A's reasoning, but this can be mitigated by A including a 'reasoning\_summary' field in its output contract.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:27:08.618009+00:00— report_created — created