Remote Control private worker unavailable and Agents Window workspace cannot be saved

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Remote Control does not work for my local Windows workspace.

When I enable /remote-control and select “This PC (Remote Control)”, every request fails with:

“Selected private worker is not available. It may have disconnected.”

The error is marked as non-retryable. Reinstalling and restarting Cursor did not resolve it.

The Agents Window also cannot save workspace settings or rename the workspace. It displays:

“Could not save this workspace. Try again.”

The project is stored locally in a OneDrive folder. Normal local Cursor access works, but Remote Control and Agents Window cloud-backed workspace settings fail.

Request IDs:
5191d71a-85c0-4bd7-871b-00e7e009e4e1
b83db0fa-965a-406a-b46b-4dffbb730dee

Steps to Reproduce

  1. Open a local Windows workspace stored in a OneDrive folder.
  2. Open the Agents Window.
  3. Enable Remote Control under Settings > Agents.
  4. Create a new local Agent session.
  5. Run /remote-control.
  6. Confirm that “This PC (Remote Control)” is selected.
  7. Send any message.
  8. The request immediately fails with “Selected private worker is not available. It may have disconnected.”
  9. Edit the workspace name and click Save.
  10. The workspace also fails to save with “Could not save this workspace. Try again.”

Expected Behavior

Remote Control should register an available worker on this computer, allow the session to appear in the Cursor iOS app, and execute tools against the local workspace. Agents Window workspace names and settings should also save successfully.

Screenshots / Screen Recordings

bug01.png
bug01.png686×361 11 KB
bug02.png
bug02.png606×452 15.9 KB

Operating System

Windows 10/11

Version Information

Version: 3.18.25 (user setup)
VS Code Extension API: 1.128.0
Commit: 280eca2911f1774689696e5f1efa5a4f97a87af0
Date: 2026-08-31T23:08:02.261Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Cursor Grok 4.6 High

For AI issues: add Request ID with privacy disabled

5191d71a-85c0-4bd7-871b-00e7e009e4e1
b83db0fa-965a-406a-b46b-4dffbb730dee

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Peter5,

For the Remote Control failure: open View > Output, pick “Cursor Agent Worker” from the dropdown (or open %APPDATA%\Cursor\User\globalStorage\anysphere.cursor-agent-worker\ and open the .log file), and paste the last several lines. I’m mainly looking for any line that mentions NODE_MODULE_VERSION.

For “Could not save this workspace”: open Help > Toggle Developer Tools, click the Console tab, reproduce the save so the error shows, and paste the red line starting with [EditWorkspace] Failed to save workspace.

Those two will tell me exactly what’s happening on each side. Thanks!