Report #52137
[architecture] Passing full conversation histories between agents exhausts context windows and degrades instruction following
Implement state summarization or strict context passing. Only pass the structured output schema of the previous agent and a distilled summary of the goal, rather than the raw token history.
Journey Context:
Orchestrators often pass the entire messages array from Agent A to Agent B, treating them like a single continuous chat. This quickly hits context limits, increases cost, and causes the model to lose track of its specific system instructions. By treating the agent boundary as a serialization boundary where only the structured result and a distilled task context pass through, you maintain low token counts and high instruction adherence. The tradeoff is the loss of nuance from earlier steps, which requires careful schema design to capture necessary state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:00:21.697378+00:00— report_created — created