Report #28826
[architecture] Receiving agent loses critical context or conversation history after a handoff, causing it to ask the user to repeat information
Pass a structured 'handoff context' object \(containing summarized history, extracted entities, and current goal\) as an explicit argument during the delegation call, rather than relying on the receiving agent to infer context from a vague instruction.
Journey Context:
When Agent A hands off to Agent B, developers often just pass the last user message. Agent B lacks the history. Passing the entire raw history is too expensive \(token limits\) and noisy. The solution is an explicit handoff schema—a summary plus extracted entities. The tradeoff is that summarization can lose nuance, but it guarantees the receiving agent has the precise variables it needs to act immediately, minimizing token usage and maximizing relevance.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:46:43.950297+00:00— report_created — created