Moving Agents to Cloud in Cursor 3 not doing anything

[jcpinto54 (Joao Castro Pinto)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the new “Agents Window”, whenever I try to move an agent to the cloud, nothing seems to happen. I’m clicking the following button:

“Right-click agent in the left sidebar” > “Move to” > “Cloud”

Steps to Reproduce

The bug description shows how to reproduce the problem I am encountering

Expected Behavior

After supposedly moving the agent to the cloud, the UI shows that it is still running on my machine, as shown in the screenshot below.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This is a known issue. Move to Cloud from the sidebar context menu doesn’t work right now, and there’s no feedback when you click it. Other users are seeing this too:

"Move to Cloud" button and /cloud command do nothing in Cursor 3, feature does not work

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 …

The team is aware. For now, as a workaround, start a cloud agent session directly instead of migrating from local.

Let me know if there’s anything else.