Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
“Move to Cloud” button and /cloud command do nothing in Cursor 3, feature does not work at all in new or existing chats for me.
Steps to Reproduce
Open a local agent chat session in the Cursor IDE editor.
Click the “Move to Cloud” button in the chat UI, OR type /cloud in the chat input and send.
Observe that nothing happens – no loading state, no error, no transition to a cloud agent.
Expected Behavior
The local agent session should be handed off to a cloud agent, as described in the Cursor 3.0 announcement: “you can move an agent session from local to cloud to keep it running while you’re offline, or so that you can move on to the next task.”
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Version: 3.0.12 (Universal) - this happens in all versions 3.0+ for me
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hi @Shadow614B
Thanks for the detailed report and recording. This is a known area of active development — the local-to-cloud migration flow in the Agents Window has had several issues that the team has been fixing recently.
A couple of things that could be contributing here:
-
Pre-3.0 chat format: You mentioned the chat was started on a pre-3.0 version and carried over through the upgrade. The cloud handoff may not fully support migrating chats that originated in the older format. Could you test whether a fresh chat started natively in 3.0 reproduces the same issue when moved to cloud? That would help narrow down whether this is a format compatibility problem.
-
Extensive conversation context: The chat had significant context (MCP tool calls, subagent spawns, browser automation, etc.). Large or complex conversation states can sometimes cause issues during the migration handoff.
As a workaround, you can start a new cloud agent session directly rather than migrating an existing local one.
Let me know if a fresh 3.0 chat also freezes when moved to cloud — that would confirm this is a broader issue rather than a pre-3.0 compatibility problem.
@mohitjain Yes, this happens on new and existing chats (started pre or post 3.0). Nothing related to moving a local chat to cloud works, including the ‘Babysit in Cloud’ button as well.
“Move to Cloud” does nothing — Cursor’s own Composer 2 Fast thought it was my fault (it’s not)
I was investigating the “Move to Cloud” button doing nothing in Cursor 3, so I asked Cursor’s built-in Composer 2 Fast model about it.
Response: very confident it was a config issue on my end — connect Git, set a default repo, pick a default model. Basically: “you didn’t set it up properly.”
Then I switched to Claude Sonnet and asked the same question. It searched the forum, found the existing bug thread in seconds, and said: “It’s a confirmed bug. Not just you.”
So: Cursor’s own proprietary model had less awareness of this known Cursor bug than an external Claude model browsing the public Cursor forum. Make of that what you will. 
The actual issue (confirmed by multiple threads):
-
The “Move to Cloud” button and /cloud command do nothing in Cursor 3 — no dialog, no error, no toast, no browser window
-
Affects: IDE button, /cloud slash command, cursor-cli cloud mode
-
Reproducible even when Git is properly connected and repo is configured
-
Some users also report cloud agents “completing” in under 5 seconds with zero changes made
Environment:
Expected: wizard, OAuth handoff, or explicit error if prerequisites are missing Actual: complete silence — no feedback whatsoever..