Remote Control handoff on Windows hangs at "Setting up environment" with self-hosted worker label mismatch error

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Executing /remote-control or changing the session target to This PC (Remote Control) from Cursor Desktop on Windows fails to establish a remote session:

The desktop prompt UI hangs indefinitely at the green “Set up Environment” status pill without returning an explicit error.

The Cloud Agent run details page shows the error: Waiting for self-hosted worker: No self-hosted worker matches the requested labels.

Transitioning older chat threads also fails due to a legacy branch sync attempt (git push origin refs/heads/master), throwing error: src refspec refs/heads/master does not match any even though local HEAD is clean on main.

Steps to Reproduce

Open a Git-backed workspace on Windows with a clean local state on main.

Open the Agents Window in Cursor Desktop (This PC mode).

Enter a prompt using /remote-control or switch the target selector to This PC (Remote Control).

Observe the session lock onto the green “Set up Environment” pill indefinitely while Cursor on iOS shows the session as offline/disconnected.

Expected Behavior

Switching target mode to Remote Control on Windows should pair the desktop worker directly with the cloud service without demanding self-hosted cloud pool setup scripts. Additionally, branch transfer should dynamically inspect current HEAD rather than executing push commands against stale thread metadata (master).

Screenshots / Screen Recordings

Screenshot 2026-08-30 140330.png
Screenshot 2026-08-30 140330.png1571×815 44.8 KB

Operating System

Windows 10/11

Version Information

Version: 3.18.9 (system setup)
VS Code Extension API: 1.128.0
Commit: 2ba48ff3f7514cc4643c52ca9f7b3173d9b66130
Date: 2026-08-27T01:42:22.092Z
Layout: Agent Window
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.26200

For AI issues: which model did you use?

Composer 2.5

For AI issues: add Request ID with privacy disabled

Request ID: bc-f9a5a256-9ba8-40aa-be10-ad1748d420ff
Canceled
Canceled
Canceled: Canceled
at x_s._confirmGitTransferFailure (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20313:379)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8745:30887

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey @Mosi_Shuchman, thanks for the detailed report.

This is a known issue we’re tracking. On Windows, the local worker process that Remote Control relies on can fail during startup, so the session never finds a machine to pair with and stays on “Set up Environment”. A fix is in progress.

To confirm you’re hitting the same thing, could you run cursor-agent worker start --verbose in a terminal and share the output? If you see an error mentioning better_sqlite3 and NODE_MODULE_VERSION, that’s the one.

8

Hey Colin,

Thanks for confirming! I tried running cursor-agent worker start --verbose, but cursor-agent.exe is not installed as a standalone CLI binary/path on my Windows setup (CommandNotFoundException).

In any case I’m glad to hear a fix is in progress for this Windows setup failure. Look Forward to the patch! Do you have an ETA for that??

Mosi