Report #78998
[architecture] Downstream agent fails to follow instructions because its context window is filled with verbose upstream agent logs
Implement a summarization and pruning step at the agent boundary. Pass only the structured output and a condensed summary of the journey, rather than the raw conversational history.
Journey Context:
Naive multi-agent systems pass the entire chat history from Agent A to Agent B. This quickly exhausts context limits and degrades instruction-following as the middle of the context gets ignored \(lost-in-the-middle\). By forcing a state transition where only the schema-contract payload and a compressed summary are handed off, you preserve the downstream agent's ability to follow its own system prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:11:35.955490+00:00— report_created — created