Report #87529
[architecture] Agent handoffs drop critical task instructions causing the receiving agent to act blindly
When handing off, the transferring agent must generate a structured 'handoff manifest' containing the original goal, current progress, and exact next steps, which becomes the primary context for the receiving agent.
Journey Context:
Just passing 'your turn' isn't enough. The new agent starts with a blank slate regarding the workflow. If it doesn't know why it was called, it will hallucinate a goal or redo work. The handoff manifest ensures continuity. It acts as a transactional boundary: the sending agent commits its state to the manifest, and the receiving agent bootstraps from it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:30:22.480293+00:00— report_created — created