Cursor Agents in Desktop app- Cloud Desktop keeps loading

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Cloud Desktop in Cursor Desktop app keeps loading and now i cannot access the terminal or browser at the right panel.

Steps to Reproduce

Click on a chat, click cloud desktop at the right panel, launch it, then close it. And the loading hangs there. now the right panel is just a loading icon in the middle.

Expected Behavior

Desktop mode is supposed to close and the terminal and browsers options are supposed to appear again

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.13 (user setup)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This is a known issue with Cloud Desktop. When you close the desktop, the panel can get stuck in a loading state. I’ve shared it with the team. There’s no timeline yet, but your report helps us prioritize it.

As a temporary workaround, try reloading the window: Ctrl+Shift+P then Developer: Reload Window. This should reset the panel state and restore access to the terminal and browser.

Let me know if that doesn’t help.

Hi,

Doesnt work either.

Try fully closing Cursor not Reload Window, but quitting the app completely, then launch it again. If that doesn’t help, open a new chat, that should reset the right panel state.

The team is aware of this bug.

Let me know if any of that helps.

nope. none of it works. i even uninstall the whole app and removed any remaining folder and reinstalled, and re-logged. still the same.

1 Like

Can you confirm which folders you deleted? On Windows, Cursor can be in a few places:

  • %APPDATA%\Cursor
  • %LOCALAPPDATA%\Programs\cursor
  • %LOCALAPPDATA%\cursor-updater
  • %USERPROFILE%\.cursor

Did you delete all four?

Even if you did, this looks tied to the cloud agent session state on the server, not local files. Try creating a completely new chat and start Cloud Desktop there, don’t open the old chat where Cloud Desktop is stuck. If it works in the new chat, the issue is with that specific session. Also try it in a different project.

Let me know how it goes.

It’s repo linked. Im using cursor cloud mode when it happens.

Another repo of mine which is also using cloud does not have this problem.

I also tried to add a new chat in cloud mode linked to the same repo, it still has that problem

hope it helps.

Since it only happens on one repo and the other one is fine, this is most likely a server-side session state tied to that specific repo. Reinstalling wouldn’t have helped.

Can you send the Cloud Agent session ID from the broken session? You can find it in the chat where you started Cloud Desktop. Open the chat menu in the top right corner, then click Copy Request ID. This will help the team check the session state on the server.

Also try one last thing: open the same repo, but start the cloud agent without using Cloud Desktop, just terminal or browser. If the right panel works without Cloud Desktop on that repo, then it’s definitely a stuck desktop session.

Let me know how it goes.

are you referring to request id? I dont see a session id.

Also try one last thing: open the same repo, but start the cloud agent without using Cloud Desktop, just terminal or browser. If the right panel works without Cloud Desktop on that repo, then it’s definitely a stuck desktop session. - I can confirm it works since im using this way right now.

Yeah, it’s the Request ID. Sorry for the confusion with “session ID”. Open the chat where Cloud Desktop is stuck, click the chat menu in the top right corner, then select Copy Request ID. Send it here and it’ll help the team check what’s going on with the server session.

Since everything works fine in the same repo without Cloud Desktop, that confirms it’s a stuck desktop session on the server side. A ticket is already open with the team, and your Request ID will speed up the diagnosis.

bc-d7981f82-0012-4890-84cf-6f1eee6716a0

1 Like