! Cursor Remote SSH regression: cursor-server locked to Node.js 20.18.2, breaking Odoo and all extensions requiring Node.js 22+

[Alex_Tk]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Remote SSH server is incorrectly locked to Node.js 20.18.2, while Cursor Desktop uses Node.js 22.21.1.
This creates a critical runtime mismatch that breaks modern VSCode extensions requiring Node.js ≥22, including the Odoo IDE extension (vscode-odoo), which requires Node.js >=22.16.0 and depends on built-in modules like node:sqlite.

Current remote error:
The Odoo IDE extension doesn’t support this environment (Node.js 20.18.2).
The extension requires Node.js >= 22.16.0.
Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite

Direct verification from remote host:
~/.cursor-server/bin/linux-x64/3e548838cf824b70851dd3ef27d0c6aae371b3f0/node -v
v20.18.2
~/.cursor-server/bin/linux-x64/3e548838cf824b70851dd3ef27d0c6aae371b3f0/node -p “process.version + ’ | ’ + process.versions.v8”
v20.18.2 | 11.3.244.8-node.23

Impact:
Cursor Remote SSH is currently unusable for production Odoo development and any remote workflow requiring modern extensions.

This is not an extension bug — Cursor remote runtime is outdated and incompatible.

Steps to Reproduce

1. Install Cursor IDE version 3.2.16 on macOS (Apple Silicon)
2. Connect to a remote Ubuntu 22.04 server using Cursor Remote SSH
3. Allow Cursor to install/update ~/.cursor-server on the remote machine
4. Verify remote runtime:
   ~/.cursor-server/bin/linux-x64/3e548838cf824b70851dd3ef27d0c6aae371b3f0/node -v
5. Confirm remote server uses Node.js v20.18.2 instead of Node 22.x
6. Install the Odoo IDE extension (vscode-odoo) or any extension requiring Node.js ≥22.16.0
7. Open any workspace/project remotely via SSH
8. Wait for extension host initialization
9. Extension immediately fails with:
   The Odoo IDE extension doesn’t support this environment (Node.js 20.18.2).
   The extension requires Node.js >= 22.16.0.
   Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite

Result
Remote extension host crashes because Cursor Remote SSH deploys outdated Node.js 20.18.2 while local Cursor Desktop runs Node.js 22.22.1.

Expected Behavior

Cursor Remote SSH server must use the same Node.js major version as Cursor Desktop (Node 22.x), or provide a supported way to override/update remote runtime.
Remote extension host should not run an outdated Node version that breaks extension compatibility.

Expected result:
Odoo IDE extension loads normally
node:sqlite available
Remote environment parity with desktop Cursor

Operating System
MacOS (Apple Silicon)
Remote Host: Ubuntu 22.04 Linux

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

This regression severely disrupts professional remote development workflows.

The same extensions work correctly in:
VSCode Remote SSH
Antigravity IDE
Local Cursor
They fail only in Cursor Remote SSH because Cursor ships an obsolete remote runtime.

This directly blocks:
Odoo development
Extensions using node:sqlite
Extensions using node:test
Modern VSCode ecosystem tools

I already verified the runtime manually, removed ~/.cursor-server, and reinstalled — Cursor still deploys Node 20.18.2 remotely.
This is a Cursor platform regression, not user misconfiguration.

This issue is actively slowing down production work and makes Cursor unreliable for remote engineering until resolved.

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey Alex. This is the same issue you reported back in February: Cursor remote runtime locked to Node 20 — breaks modern extensions requiring Node ≥22 (node:sqlite). Confirming it is a known bug. The remote cursor-server really does pin Node 20.18.2 in the build configuration, while desktop is already on Node 22.x.

We are tracking this on our side, but to be transparent, it has been in the backlog since February and there is no ETA for the upgrade yet. I will add a note to the existing ticket that Odoo IDE is now affected too. That increases the impact since before it was mostly users hitting this with MCP and node:sqlite.

There is no workaround at the remote runtime level. A PATH override via server-env-setup does not work, see the related known issue with nvm in WSL or SSH. If you can, please temporarily keep the Odoo workflow in local Cursor or use VSCode Remote SSH until the upgrade ships.