Report #21172
[architecture] Passing full conversation histories between agents causes context overflow and instruction forgetting in downstream agents
Implement a 'contractual handoff' where the upstream agent outputs only a structured summary \(state \+ artifacts\) required for the next step, rather than the raw chat history.
Journey Context:
To preserve state, developers often pass the entire message array from Agent A to Agent B. As the chain grows, Agent B spends its context window on irrelevant history and drops its system prompt. The fix is to treat agent boundaries as serialization points. Agent A's final output must be a distilled, structured payload \(the 'contract'\). Agent B starts fresh with only its own system prompt and the contract payload. Tradeoff: Loss of subtle context from earlier steps; requires careful schema design to ensure all necessary state is captured.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:56:44.568461+00:00— report_created — created