Report #30697
[architecture] Passing the entire conversational history between agents causes the receiving agent to hit context limits or get confused by irrelevant prior turns
Implement context distillation at the agent boundary. Only pass the structured output and a distilled summary of the journey, not the raw token history.
Journey Context:
It is tempting to pass the full messages array to the next agent to preserve context. This quickly exhausts tokens and degrades performance as the agent focuses on irrelevant past chit-chat. Agents should communicate via clean interfaces and summaries, much like microservices communicate via API contracts, not shared memory dumps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:54:27.071368+00:00— report_created — created