Cursor Remote Control on Windows stuck on "Waiting for a worker": `better_sqlite3.node was compiled against a different Node.js version using NODE_MODULE_VERSION 127. This version of Node.js requires

发生场景

Source(s): https://forum.cursor.com/t/remote-control-worker-crashes-on-windows-better-sqlite3-node-module-version-127-vs-137/168419 Signal: 588 views, 15 posts; staff tracked it for two months; several "same here" reports on Windows 10 and 11 (Aug–Oct 2026). Status: reported working by source, not reproduced by us.

问题

On Windows, a Remote Control session shows up on the Cursor web Agents page, but Cursor Desktop stays on "Setting up environment" / "Waiting for a worker" and the web session says "Waiting for self-hosted worker". The worker log shows it starts, authenticates and registers, then exec-daemon fails with the error above and the worker exits with code 1. The standalone CLI (agent worker start) fails the same way. Normal local agent runs work.

报错原文（已脱敏/规范化）

Error starting exec-daemon:
better_sqlite3.node was compiled against a different Node.js version using NODE_MODULE_VERSION 127.
This version of Node.js requires NODE_MODULE_VERSION 137.

Selected private worker is not available

适用环境

Windows 10/11 x64, Cursor Desktop 3.15.x to 3.25.x, Cursor Agent CLI / worker builds up to 2026.10.14.

如何确认是这个问题

1. The worker log contains NODE_MODULE_VERSION 127 and requires NODE_MODULE_VERSION 137 right after the worker registers. → expect: the worker exits with code 1.
2. agent --version → expect: older than 2026.10.16 (staff said the 2026.10.14 builds were released before the fix).

不是这个问题时 / 边界

The worker log shows a different error, or you are on 2026.10.16 or newer and it still crashes (staff asked for agent --version output and the worker log in that case). WSL was discussed as a substitute, but staff and users said it is not one when the repo and toolchain live on Windows.

根因

Staff confirmed a packaging bug: the native better-sqlite3 binary bundled with the Windows agent CLI was built for Node ABI 127, while the bundled Node runtime needs ABI 137, so exec-daemon crashes right after the worker registers. Staff also said the network (HTTP/2 vs HTTP/1.1) is not involved.

修复步骤

1. Remote Control / Agents Window: fully close Cursor and open it again; the worker downloads the new version automatically (staff). → expect: the worker is on Cursor Agent CLI 2026.10.16 or newer, which staff said contains the fix. A commenter on the 2026.10.14 build replied "It works for me" after this update.
2. Standalone CLI: run Cursor's official Windows install command again in PowerShell (staff posted irm 'https://cursor.com/install?win32=true' | iex), then run agent --version. → expect: 2026.10.16 or newer; then run agent worker start again.
3. Make sure Git for Windows with Git Bash is on PATH; staff said that without it the Windows worker may not pick up tasks.

如何验证

The Remote Control session leaves "Waiting for a worker" and a simple prompt runs on the Windows machine; the worker log no longer shows the NODE_MODULE_VERSION error.

试过没用的办法

Regenerating the Cursor-managed agent CLI folder (the original poster; the bad binary ships in the bundle), switching Cursor's HTTP compatibility mode to HTTP/1.1 (the original poster; diagnostics went green but the worker still crashed), and re-downloading the 2026.10.14 worker (a commenter).

风险提示

Before the fix, the original poster, following a commenter's suggestion, replaced the bundled better_sqlite3.node by hand with a prebuilt binary from the better-sqlite3 GitHub releases. Staff called that a temporary manual workaround and said it is no longer needed on 2026.10.16+ because the new version installs into a separate folder. Don't drop downloaded native binaries into Cursor-managed folders (our inference), and don't run npm rebuild on the managed files (staff advised against it).

验证范围

Cursor Agent CLI on Windows, builds before 2026.10.16 (Aug–Oct 2026).

何时失效

No pre-2026.10.16 Windows worker builds remain in use.