[Windows] agent worker start fails: better-sqlite3 NODE_MODULE_VERSION 127 vs 137 — Remote Control broken

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

On Windows, agent worker start crashes when starting exec-daemon. The native module better-sqlite3 was built for NODE_MODULE_VERSION 127 but the bundled Node.js requires NODE_MODULE_VERSION 137.

Because the self-hosted worker never stays online, Remote Control sessions fail with:

  • Waiting for self-hosted worker
  • No self-hosted workers are connected
  • No self-hosted workers were available for this repo

Git push issues were fixed separately. This looks like a broken cursor-agent Windows package.

Environment:

  • OS: Windows 10/11
  • Cursor desktop: 3.15.19 (user setup), VSCode Extension Version: 1.128.0, Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0
  • Workspace: D:\Game
  • Git remote: rain294890061/Game on GitHub
  • cursor-agent path: C:\Users\rainwang\AppData\Local\cursor-agent
  • Agent version folder: 2026.08.11-e8db854
  • Plan: Pro
  • Cursor Version: 3.15.19

Steps to Reproduce

  1. Install Cursor Agent CLI on Windows using the official win32 install script from Cursor docs (PowerShell).

  2. Run: agent login (success)

  3. cd D:\Game (git remote is rain294890061/Game on GitHub)

  4. Run: agent worker start --name game-pc --debug

  5. Worker crashes immediately with:
    Error starting exec-daemon: better_sqlite3.node was compiled against a different Node.js version.
    NODE_MODULE_VERSION 127. This version of Node.js requires: NODE_MODULE_VERSION 137.

  6. Remote Control also fails: enable Remote Control in Agents Window, send /remote-control plus a follow-up, then open the session on the web Agents page — shows no self-hosted workers connected, fails after 40 attempts.

Also tried:

  • Delete LOCALAPPDATA\cursor-agent and reinstall CLI — same error
  • PowerShell ExecutionPolicy Bypass — login works, worker start still fails
  • I sometimes use remote desktop to access this PC, but the sqlite version error happens on the machine itself, not only over remote desktop

Expected Behavior

agent worker start should keep running and register a self-hosted worker for rain294890061/Game.

Remote Control (/remote-control plus follow-up in Agents Window) should allow continuing the session from the web Agents UI or mobile, with tool calls on the local Windows machine.

Screenshots / Screen Recordings

download.png
download.png1351×424 16.8 KB
微信图片_20260813144456_64_110.jpg
微信图片_20260813144456_64_110.jpg1080×2400 184 KB

Operating System

Windows 10/11

Version Information

Version: 3.15.19 (user setup)
VS Code Extension API: 1.128.0
Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0
Date: 2026-08-11T05:22:54.627Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. This is the same issue as in this thread: Windows Remote Control worker crashes — better-sqlite3 NODE_MODULE_VERSION 127 vs 137 — Cursor 3.15.6. Reinstalling the CLI won’t help here, since it’s caused by a native module inside the Windows package itself, not your setup. We’re tracking it.

For now, the working workaround is to run the worker in WSL, since the Linux build works fine:

  1. Install Ubuntu via WSL
  2. Inside WSL: curl https://cursor.com/install -fsS | bash CLI Installation | Cursor Docs
  3. Run agent login, then from a repo that lives inside the WSL filesystem, not in /mnt/c: agent worker start

Important: the repo must be inside the WSL filesystem, not /mnt/c/... or D:\Game, otherwise you’ll hit issues. So you’ll need to re-clone D:\Game into WSL.

I can’t share a timeline for the native Windows package yet, but I’ll reply here when there’s an update. Let me know if the WSL option doesn’t work on your side.