Report #21209
[architecture] An agent takes on the persona or instructions of another agent after a handoff, losing its specialized focus
Strictly scope system prompts and reset the agent's identity context upon receiving a handoff. Use distinct, non-overlapping toolsets to physically prevent identity bleed.
Journey Context:
When an agent receives a long chat history from another agent, it often gets confused and tries to act like the previous agent \(e.g., a planner trying to write code\). You must clearly delineate the handoff payload from the agent's own system instructions. The tradeoff is that isolating context means the agent might miss subtle cues from the history, but this is preferable to an agent executing tools it wasn't designed to use.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:00:41.012801+00:00— report_created — created