Interrupting in the middle of passing a conversation to the cloud completely cooks the session

Open

Pre-submit Checks

I have searched Warp bugs and there are no duplicates
I have searched Warp known issues page and my issue is not there
I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

After interrupting during handoff to cloud agent, conversation is completely unusable, any future messages seem to fail, not even be shown in the chat, and sort of disappear into the void. Now and then I'm able to see it attempt to start a new cloud handoff process which dissipates during step 1/3.

Note:

"I'm sorry, I couldn't complete that request. Request failed with error: ErrorStatus(403, "{"error":"valid workload token required"}")" Inline error message.
"Cloud agent run cancelled" above the chat box.

See conversation id: {"conversation_id":"fd05f874-a5c8-4f7b-b564-21ed1378c968"}

To reproduce

Click "Hand off to cloud"
Ctrl+c interrupt during handoff.
Attempt to continue conversation.

Expected behavior

Smoothly go back to local agent.

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

10.0.26200

Shell Version

No response

Current Warp version

v0.2026.10.14.08.27.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

No response

Activity

warp-for-oss[bot]9d ago

@indancisive

Here's what I found while triaging this issue:

This appears to be a cloud handoff cancellation-state bug, not a general terminal input issue. A temporary workaround is to start a fresh conversation after cancelling a handoff, because the cancelled handoff pane may remain associated with an invalid cloud state.

Maintainer details

I concluded that cancelling a local-to-cloud handoff can leave the conversation in a cancelled/invalid cloud-handoff state where later prompts fail instead of returning to local execution..

Triage summary

This looks like a local-to-cloud agent handoff cancellation bug. The reported sequence is: start Hand off to cloud, press Ctrl+C during startup, then the conversation remains in a cancelled/invalid cloud state and subsequent prompts fail or disappear instead of continuing locally.

Reproduction confidence

Medium. The report includes exact Windows/Warp versions, a short repro path, the visible Cloud agent run cancelled state, and the distinctive valid workload token required 403. The main uncertainty is timing: the bug likely depends on cancelling after the destination cloud pane/conversation fork is materialized but before the handoff fully commits.

Likely implementation area

The relevant code appears to be the local-to-cloud handoff lifecycle:

app/src/ai/blocklist/handoff/pipeline.rs forks/materializes handoff state before spawning the cloud run and returns HandoffCommitOutcome::Cancelled for cancellation before or during spawn.
app/src/workspace/view.rs handles HandoffCommitOutcome::Cancelled with an empty branch, even though materialize_handoff_target may already have opened a cloud pane and persisted the forked server conversation token.
app/src/terminal/view/ambient_agent/model.rs moves the handoff model to Cancelled and retains request/handoff state for the cancelled pane.
app/src/terminal/view/shared_session/cloud_conversation_continuation.rs and app/src/server/server_api/ai.rs are relevant for how later prompts route into cloud follow-up or spawn APIs.

A likely fix should ensure cancellation after materialization either fully restores/returns the source pane to local-agent input or makes the cancelled handoff pane safely resettable, rather than leaving a partially cloud-associated conversation that can submit follow-ups with invalid authorization context.

This is my automated analysis and may be incorrect. A maintainer will verify the details.