Cursor remote runtime locked to Node 20 — breaks modern extensions requiring Node ≥22 (node:sqlite)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor remote SSH server uses Node.js 20.18.2 while desktop Cursor uses Node.js 22.x.
Many modern VSCode extensions now require Node ≥22 and rely on built-in modules such as node:sqlite.
When such extensions run in Cursor remote environment, they crash immediately because Node 20 does not provide these modules.
Example: Odoo extension fails with ERR_UNKNOWN_BUILTIN_MODULE: node:sqlite.
The same extensions work correctly in VSCode Remote SSH and other IDEs using Node ≥22.
This creates a runtime mismatch between local Cursor and remote Cursor server that breaks extension compatibility.

Steps to Reproduce

Install latest Cursor (2.4.28).
Connect to a remote Linux machine via SSH using Cursor.
Install an extension that requires Node ≥22 (example: vscode-odoo).
Open workspace and wait for extension host to start.
Extension server crashes with error:
Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite.

Expected Behavior

Cursor remote server should use the same Node.js major version as desktop Cursor (Node 22),
or provide a way to configure/override Node runtime for the remote extension host.
Extensions that require Node ≥22 should run normally in remote environments.

Operating System

MacOS

Version Information

Client: macOS (Apple Silicon)
Remote: Ubuntu 22.04 (SSH)

Version: 2.4.28
VSCode Version: 1.105.1
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Remote cursor-server Node version: 20.18.2

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

This issue affects any extension that relies on Node ≥22 APIs (node:sqlite, node:test, newer Node built-ins).
Extensions work in:
VSCode Remote SSH
Antigravity IDE
Local Cursor
They fail only in Cursor remote SSH due to outdated Node runtime (20.x).
Remote runtime appears locked to Node 20 and does not update automatically with desktop Cursor runtime.
The same extensions run correctly in VSCode Remote SSH and Antigravity,
which use newer Node runtimes for their extension hosts.

CURSOR IDE
Version: 2.4.28
VSCode Version: 1.105.1
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Local Node.js
➜ ~ node -v
v22.22.0

Antigravity
Chromium: 39.2.3
Node.js: 142.0.7444.175
V8: 22.21.1
ОС: 14.2.231.21-electron.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the detailed report. The exact versions and the comparison with other IDEs were really helpful.

This is a bug. The remote cursor-server is currently using Node.js 20.18.2, while the desktop client ships with Node.js 22.x. Because of that, any extensions that depend on Node APIs from 22 or newer, like node:sqlite, will crash in the remote environment.

I’ve passed this on to the team.

How long will it take you to fix the bug?

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.