Report #61704
[architecture] Loss of conversational context or instruction bleed during agent handoffs, where the receiving agent acts on stale or conflicting system prompts
Pass explicit, minimal context variables \(scratchpads\) during handoffs rather than dumping the entire chat history, and strictly isolate system prompts per agent.
Journey Context:
When Agent A hands off to Agent B, developers often pass the full message history. This fills B's context window with A's internal reasoning, confusing B and causing it to adopt A's persona. Alternatively, passing no history causes B to ask the user to repeat themselves. The solution is to pass structured context variables alongside the user's core request, while letting B rely on its own isolated system prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:03:41.353550+00:00— report_created — created