Handoff from cloud to cloud

Cloud-to-cloud handoff in Warp lets you send follow-up instructions to a finished cloud agent run and continue it in a fresh cloud session. The run keeps the same conversation and restores the prior workspace state, so the agent can pick up where it left off instead of starting over.

Watch this walkthrough to see how cloud-to-cloud handoff continues a cloud agent run without losing the prior session context.

Use this handoff direction when:

• You want to send a follow-up to a cloud agent after its session has ended.
• You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the Agent Management Panel in the Warp app and the Runs page in the Oz web app.

What carries over

When you send a follow-up to a run whose session has ended, the run continues with:

• The same conversation - The follow-up is appended to the same conversation. From your perspective, the run is one continuous conversation across sessions.
• The prior workspace state - The prior session’s repository changes (tracked and untracked) are restored before the agent answers your follow-up. For Git-managed sessions, the new session continues on the same Git branch. You can customize which repositories and files get snapshotted when running outside the bundled cloud agent image.
• Stable run identity - The run’s ID, task, creator, environment, schedule trigger, and integration source are preserved. Compute usage is recorded per session but rolls up to the same run.

If any changes fail to apply, the agent reports which changes failed and continues with the changes that applied cleanly.

Prerequisites

• An ended cloud agent run - The run must be in a terminal state, such as succeeded, failed, or canceled, and have an associated agent conversation. Blocked runs that are waiting on user input or approval can’t be continued via cloud-to-cloud handoff; respond to the prompt on the original run instead. Very old runs that predate the agent conversation model can’t be continued via handoff.
• A snapshot from the prior session - Cloud agent runs capture a workspace snapshot at the end of each session. If the prior session couldn’t capture one (for example, due to a transient storage error), the run still continues but without restored workspace state.
• Access to the run - You need permission to submit follow-ups for the run. For team runs, this is typically any team member. Cloud runs that originated from a local-to-cloud handoff can be continued only by the user who created them, not by other team members.

Caution

Cloud-to-cloud handoff relies on a snapshot from the prior session. Older cloud runs that don’t have a snapshot on file can’t be handed off; start a new run instead.

Sending a follow-up

To continue an ended cloud run, open the run in Warp and send the next message in the conversation. When the original session has ended, Warp automatically starts a fresh cloud session and restores the prior workspace state.

1. Open the ended cloud run. Find it on the Runs page in the Oz web app or in the conversation panel in the Warp app.
2. Send your follow-up. Enter the next message in the conversation’s input and submit it.

The run picks up where it left off, with workspace state restored.

Third-party agent runtimes

Cloud-to-cloud handoff also works for supported third-party agent runtimes, but the flow is slightly different from Warp Agent runs:

1. Open the ended run from the conversation panel in the Warp app, or from the artifacts shown after the run completes.
2. Click Continue.
3. Type your follow-up prompt and submit it.

Inspecting a run that’s been handed off

The Agent Management Panel in the Warp app and the Runs page in the Oz web app show one row per run, even when the run spans multiple sessions.

1. Open the Agent Management Panel in the Warp app or the Runs page in the Oz web app.
2. Select the handed-off run.
3. Review the transcript. Each session appears in order, so you can see where one session ended and the next began.

Per-session timestamps aren’t currently exposed in the API; the transcript is the source of truth.

Troubleshooting

The run continued but no workspace state was restored. The prior session didn’t capture a snapshot. This is rare but possible because snapshot capture is best-effort. The run still continues with the same conversation, so the agent has the full transcript context even without the workspace state.

The run is in a terminal state with no conversation and follow-ups are rejected. Very old runs predate the agent conversation model and can’t be continued via handoff. Start a new cloud agent run with the prompt you want, referencing the prior run if needed.

Related pages

• Handoff overview - What handoff is, the directions it supports, and what carries over.
• Handoff from local to cloud - Promote a local conversation to a cloud run.
• Managing cloud agents - Find runs to send follow-ups to.