Report #52535
[architecture] Accumulated conversation history from multiple agents exceeds context limits or poisons the downstream agent's focus with irrelevant intermediate steps
Do not pass raw conversation history between agents. Pass only the strictly necessary structured output \(the schema contract\) and a distilled summary of relevant context.
Journey Context:
When Agent A hands off to Agent B, developers often pass the entire messages array so B has 'full context.' This is an anti-pattern. It leaks internal reasoning, exposes system prompts, and wastes tokens. Worse, B might start acting on instructions meant for A. The correct pattern is to treat the agent boundary as a trust and context boundary. A must distill its findings into the agreed-upon schema contract, and the orchestrator passes only that payload to B, along with B's specific system prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:40:24.109174+00:00— report_created — created