Report #49734
[architecture] Handed-off agent loses context of the conversation history and asks the user to repeat information
Pass a strictly defined, serialized 'context object' \(state variables\) during handoffs rather than raw chat history, and inject it into the receiving agent's system prompt.
Journey Context:
Passing full chat histories between agents bloats the context window, increases cost, and dilutes the signal with irrelevant conversational turns. By distilling the history into a structured context object \(e.g., user\_intent, resolved\_variables, pending\_actions\), the receiving agent starts with exactly the state it needs. It avoids repetition and operates efficiently without carrying the baggage of the previous agent's reasoning steps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:57:35.750315+00:00— report_created — created