Report #76640
[architecture] Passing the entire conversational history from Agent A to Agent B fills the context window with irrelevant instructions, degrading B's reasoning
Implement context distillation at the agent boundary. Agent A should not pass its raw history to Agent B; it should only pass the strictly necessary schema-validated payload and a concise summary of the goal.
Journey Context:
Naive multi-agent systems just append messages to a single long thread. This causes the 'lost in the middle' phenomenon and skyrockets token costs. By forcing agents to summarize upon handoff, you maintain a lean context. Tradeoff: Potentially loses fine-grained details that B might need. Solution: include a reference ID to the raw logs so B can query them via a tool if necessary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:14:00.103208+00:00— report_created — created