When agent checks node version it outputs its own sandboxed version

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the agent wants to check the users node version it runs node -v but sees the wrong version. I believe it sees its own sandboxed version.

This leads to many issues when the agent is trying to debug the users problem.

Steps to Reproduce

  1. Open cursor (no project needed)
  2. Open chat panel
  3. Tell agent: “Check my node version.”
  4. Run node -v in terminal and see that the versions do not match

Expected Behavior

Agent should see users node version, not its own.

Screenshots / Screen Recordings

agentnodev.png
agentnodev.png443×304 9.47 KB

Operating System

Windows 10/11

Version Information

Version: 3.5.33 (user setup)
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
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: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

Composer 2.5, but happens with all models.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hi @post4k , Thanks for reporting this! This is a known issue… we’ll let you know when it’s sorted out.

9

Hi @post4k — good news: we tracked this down and a fix has been merged. As you suspected, the agent terminal was resolving node to Cursor’s bundled runtime instead of your system Node, because our server was prepending its own Node to PATH. The fix stops that, so the agent will pick up your installed Node version.

It hasn’t rolled out to the stable release just yet — it’ll land in an upcoming update. Once you’re on a version that includes it, node -v from the agent should match your terminal. We’ll keep this thread posted, and thanks again for the clear repro!