AI Agent Handoff
In short: An AI agent handoff moves an unfinished job to another model or agent with its session trail, completed results, pending work, and receipt links intact. The handoff preserves the work without pretending a plan is a completed execution.
Moving work between AIs
A useful handoff names what is complete, what is pending, and where the evidence lives. Give the receiving agent the stable session ID and relevant receipt URLs, then have it inspect prior results before continuing.
Session persistence across models
The session trail stores tool results server-side. That makes the execution history available to a different model while keeping the boundary between completed work, planned work, and failed work explicit.
FAQ
An AI agent handoff moves an unfinished job to another model or agent with its session trail, completed results, pending work, and receipt links intact.
An agent handoff is a controlled transfer of work state, not a claim that the receiving agent completed the task.
A stable session ID lets the receiving model retrieve earlier server-side tool results, while receipts show what already happened and what remains.
Read the cross-AI continuity answer · Read the AI agent receipt guide · Read about AI agent proof · Install the Zambo MCP