Report #53056
[architecture] Passing full chat history between agents exhausts context windows and degrades instruction following
Implement a context contract where agents only pass strictly necessary structured summaries across boundaries, discarding raw conversational history.
Journey Context:
It is tempting to pass the entire messages array from Agent A to Agent B so B has full context. However, this quickly hits token limits, increases latency, and causes the lost-in-the-middle phenomenon where B ignores its system prompt. The better pattern is for Agent A to output a structured state object \(the context contract\), and the orchestrator initializes Agent B with only its own system prompt plus this state object.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:32:52.786971+00:00— report_created — created