[Bug] IDE Chat unavailable in Cursor Remote SSH with Node.js 20 extension host #1036

Summary

Command Code IDE extension v0.2.3 cannot launch its native Chat panel when installed in the remote extension host of Cursor 3.18.25 via Remote SSH.

The extension displays:

Command Code chat needs VS Code 1.106 or later. Terminal integration still works.

The same extension works when installed locally on Windows.

Investigation suggests that the compatibility check depends on the Node.js version bundled with the Cursor remote extension host (v20.18.2), rather than the system-installed Node.js version (v22.6.0).

This prevents me from using the native IDE Chat interface to work directly with code on a remote GPU server, although the Command Code CLI works correctly in the remote terminal.

Expected Behavior

I would like to use Command Code's native Chat panel in Cursor while working on projects over Remote SSH.

Ideally, the extension should support remote extension hosts running Node.js 20 if technically feasible.

Alternatively, an officially supported compatibility solution would be helpful, such as allowing the Chat UI to run locally while the agent's file and shell tools operate on the remote server.

If Node.js 22 is a strict technical requirement, the extension should clearly document this requirement for Remote SSH environments and explain the supported migration options.

Actual Behavior

When Command Code v0.2.3 is installed under SSH: GPU, the native Chat panel refuses to start and displays:

Command Code chat needs VS Code 1.106 or later.
Terminal integration still works.

The remote Cursor Server bundles Node.js v20.18.2, even though the system-installed Node.js has already been upgraded to v22.6.0.

The Command Code CLI works normally in the remote terminal.

I also tested forcing the extension to run locally using:

{
  "remote.extensionKind": {
    "CommandCode.commandcode-vscode": ["ui"]
  }
}

This allows the Chat panel to open, but does not provide a verified solution for operating on the remote workspace, because the agent runtime executes locally.

Therefore, neither the current remote IDE Chat setup nor the local UI workaround provides the native remote development experience I need.

Steps to reproduce the issue

1. Open Cursor 3.18.25 on Windows.
2. Connect to a Linux GPU server using Remote SSH.
3. Install Command Code extension v0.2.3 in the SSH: GPU extension host.
4. Open the Command Code Chat panel.
5. Observe the compatibility warning requiring VS Code 1.106 or later.
6. In the remote terminal, check the bundled Node.js version:

find ~/.cursor-server/bin -maxdepth 5 -type f -name node \
  -exec sh -c 'echo "$1"; "$1" -v' _ {} \; 2>/dev/null

The installed Cursor Server runtimes report Node.js v20.18.2.

7. Verify the system-installed Node.js version with node -v, which reports v22.6.0.
8. Install or open Command Code in a local Cursor window. Its native Chat panel opens successfully.

The issue appears specific to the remote extension-host runtime.

Command Code Version

1.82.5

Operating System

Linux

Terminal/IDE

Cursor 3.18.25 via Remote SSH

Shell

zsh

Session file (optional)

No response

Fix prompt (optional)

Investigate the Node.js runtime compatibility check in the Command Code VS Code extension.

The installed extension appears to use a check equivalent to:

Number.parseInt(process.versions.node.split(".")[0]) >= 22

Please determine:

1. Which native Chat features actually require Node.js 22.
2. Whether Chat can support Node.js 20 remote extension hosts with a compatibility implementation.
3. Whether a local Chat UI can communicate with an agent running on a Remote SSH host while preserving remote filesystem and shell operations.
4. Whether the compatibility warning should explicitly mention the remote extension-host Node.js requirement instead of only the VS Code version.

The fix should be tested in a Cursor Remote SSH environment with Node.js 20 in the extension host, while preserving existing Node.js 22+ behavior.

Please do not simply remove the version guard unless the required APIs are verified to work.

Additional context

Environment details

The remote Cursor Server contains multiple linux-x64 and linux-legacy-x64 installations, all reporting Node.js v20.18.2.

Upgrade constraint

The remote GPU server uses glibc 2.27. Upgrading Cursor may deploy a newer remote server requiring glibc 2.28 or later, potentially breaking an otherwise working Remote SSH connection.

I would therefore prefer a compatibility fix that does not require upgrading Cursor or replacing the existing remote server environment.

The glibc version is an upgrade constraint, not a confirmed cause of the current Chat initialization error.

Available workaround

The Command Code CLI works in the remote terminal. However, I would prefer to use the native IDE Chat panel, including session navigation, editor context integration, and code review capabilities.

Please let me know whether compatibility with older Cursor remote extension hosts is planned.

I can provide additional logs and test a potential fix if needed.