Hand off an AI conversation
Transfer control to a teammate at a safe turn boundary, keeping saved context intact.
On this page
Before you hand off
The recipient must already have room editing access. For an outside guest, first follow Let a guest help with code. To run the next prompt, the recipient also needs their own connected computer and configured AI tool.
Handoff transfers control of the conversation. It does not migrate a running process, transfer provider credentials, or copy unsynced local files. Keep the current computer online until its turn finishes and saved work uploads.
Offer the chat
- While driving the chat, select Handoff in the file-manager action area.
- Review the conversation briefing. Update it if needed, then optionally select Use briefing in handoff note.
- Choose a specific eligible teammate or Any room editor.
- Add a short note about the next action or remaining checks.
- Select Offer handoff.
An offer expires after one hour. You can cancel a pending offer. A specifically invited recipient can decline it.
Accept and continue
The recipient opens the chat and selects Accept control. Acceptance stays disabled while the current turn is running. Once accepted, the UI shows the new driver.
Accepting does not run a task or spend AI usage. Read the briefing, inspect the transcript and saved changes, and check uploaded checkpoints before sending the next prompt from your own computer.
Recent handoffs remain visible in the dialog. If you want a separate conversation instead, fork the chat.
When the previous driver is unavailable
A room owner can use Recover unavailable driver / abandoned turn when recovery is permitted. This changes control of available saved state; it does not retrieve files that never uploaded.
Open Activity & checkpoints and distinguish saved work from unconfirmed local progress before continuing. If an action reports a newer control version, refresh and review the current driver rather than repeating an old action blindly.