Cursor CLI 2026.10.16 fixes the Windows worker crash

If your Windows PC never showed up as a worker for Cursor's Remote Control or cloud agents, update the Cursor Agent CLI to 2026.10.16 or newer and install Git for Windows. Cursor staff member deanrie said at 2:50 PM ET on Oct 16 that the crash "is fixed in Cursor Agent CLI version 2026.10.16 and newer."

What changed#

Since at least Aug 13, agent worker start on native Windows registered and then crashed, because a bundled database module was built for a different Node version ("NODE_MODULE_VERSION 127" vs 137). Sessions sat on "Waiting for a worker." On Aug 14, deanrie wrote "there's no user-side workaround right now." By Oct 12 the only options were to keep the desktop app open or run the worker in WSL. A user reported it "Still broken on the latest Cursor CLI, 2026.10.14-0f9edde" on Oct 14.

Now, deanrie says, "the lightweight CLI worker should now work directly on Windows, without WSL and without the desktop app being open." Staff member kevinn added that tasks started from the mobile app "should move past 'Setting up environment.'" One user replied at 4:11 PM ET: "It works for me !"

Why it matters#

Our read: a Windows PC can now take cloud agent tasks on its own, with your files and tools, and you can start them from your phone. One user in the thread wanted it so GrokBot could "delegate Python coding and VectorBT Pro backtesting to a local Windows machine containing large datasets."

How to use it#

1. Remote Control or Agents Window: "fully close Cursor and open it again. The worker will download the new version automatically" (deanrie).
2. Standalone CLI: run agent update, or rerun the installer in PowerShell:

irm 'https://cursor.com/install?win32=true' | iex
agent --version
agent worker start

3. Check that agent --version shows 2026.10.16-e3cb207 or newer (deanrie).
4. Install Git for Windows before you start the worker (see below).

Good to know#

• Git Bash is now required. deanrie says the Windows worker "now uses Git Bash and won't start without it" (post), and in another post that without it on PATH "the worker may not pick up tasks." Either way, install it.
• 2026.10.14 is too old. Those builds "were released before the fix" (post).
• Undo nothing by hand. If you swapped in your own better_sqlite3.node, deanrie says that's "no longer needed," since the new version installs into a separate folder.
• Still failing? deanrie asks for "the output of agent --version and the full error text."

What to watch#

More user confirmations in the main thread. Cursor's changelog has no entry for this CLI build yet (latest is Oct 13).