[BUG] Claude Code requires Node.js version 18 or higher to be installed.

I also encountered this issue. My node is v20.19.3

<img width="2488" height="1123" alt="Image" src="https://github.com/user-attachments/assets/e731c052-3281-437d-acc9-2eeecc8f81cf" />

@HenryLian66 use it from the command line for now, don't use it in vscode like that

Awesome session limit reached with no warning it's about to end, y'all really did great with 2.0!

I have also encounter same problem with nodejs version v24.9.0.

And thanks about @syfenx , the suggestion about to run claude code with command line works for me.

The same problem with node v22.14.0.

Same problem.
Node v22.19.0

Cursor
Version: 1.7.12 (user setup)
VSCode Version: 1.99.3
Commit: b3f1951240d5016648330fab51192dc03e8d7050
Date: 2025-09-28T00:58:08.696Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

IDE is run under WSL

Im also experiencing the same issue.
MacOS : 26.0.1
Node.js : v20.19.4

Same problem
node --version
v18.20.6

Same problem here

node --version
v18.20.8

I had the same error with Node v22.13.1 installed.
Reinstalling claude-code helped, along with updating the VS Code plugin and restarting VS Code.

I had the same error with Node v22.13.1 installed. Reinstalling claude-code helped, along with updating the VS Code plugin and restarting VS Code.

Same for me. Works after reinstalling claude-code and restarting VSCode

same, Nodejs v22.6.0
reinstalled claude code, reinstalled vscode extension, restarted - didn't work!

Getting the same.

Update / Resolution

Initially saw the message:
“Error: Claude Code requires Node.js version 18 or higher to be installed.”

Steps taken:

Installed Node.js ≥18 both locally (macOS, v24.1.0) and on the cluster via nvm (v20.19.5), verified in both bash and /bin/sh.

Confirmed the environment was configured correctly, but the error persisted.

Later, a new error appeared:

API Error: 401 ... OAuth token has expired

Fix:

Logged out of the extension, uninstalled it, reinstalled, and re-authorized when prompted.

After this, Claude Code started working locally and in Remote-SSH sessions as well.

How did you uninstall claude?

Environment:

• Windows 11 with WSL2
• Cursor running on Windows, project located in WSL filesystem
• Node.js installed in WSL only

Temporary Solution

Install Node.js on Windows host system (not just WSL)

I have the same issue with node v24.3.0 and Claude Code v2.0.1

Reverting the VSCode extension to v1.0.127 has resolved the issue (the issue also exists in 1.0.128)

Same problem here

For context: I'm on a Macbook Pro M1 Pro. Both projects use the same Node version: v18.20.4.

I have separate VSCode windows for each project.

In Project A (opened yesterday): Claude Code works after restarting the extension.

In Project B (new window): Claude Code shows the error from this issue.

Important: When I run the same Project B from an external terminal, Claude Code works fine. This suggests the issue is specific to the VSCode environment for this project.

same issue here on node v22

Mine started working after I reinstalled claude-code on Ubuntu and updated VS Code to the latest version.

npm uninstall -g @anthropic-ai/claude-code
npm install -g @anthropic-ai/claude-code

finally restarted VS Code.

Restarting Cursor solved the issue in my case

Same issue and I'm on Node v22.14.0. Tried the following but the issue remains:

• logging out of the Claude Code extension in VSCode and reinstalling it
• uninstall/reinstall of @anthropic-ai/claude-code
• restarting VSCode

Same issue and I'm on Node v22.14.0. Tried the following but the issue remains: logging out of the Claude Code extension in VSCode and reinstalling it uninstall/reinstall of @anthropic-ai/claude-code * restarting VSCode

For me, simply restarting the VSCode works. I'm on macOS 26.0.1 and Node v24.5.0

As mentioned above, the problem was not solved after reinstalling and I still cannot use it.

Same problem. I tried uninstall/reinstall/restart, and also have Node 22 installed on both WSL and Windows host.

I solved it by adding a global Node.js version. I use asdf so I added nodejs 22.20.0 to ~/.tool-versions and it fixed the issue.

For me it works if I launch vscode from the terminal using the command ``code``. It seems that when we launch the vscode using the shortcut/icon it doesn't load the PATH or something like that, maybe it is not a Claudes bug, but they can try to load the PATH from the extension as well.

Can you guys try to see if it works for you?

Same. Attempted uninstall/reinstall, etc., and launch from cmd. No luck.

Workaround found: I managed to bypass this issue by:

1. Downgrading the Claude Code extension to v1.0.123
2. Restarting VSCode
3. Launching Claude Code - it then successfully loads version 2.0.0

For me it works if I launch vscode from the terminal using the command code. It seems that when we launch the vscode using the shortcut/icon it doesn't load the PATH or something like that, maybe it is not a bug of Claude, but they can try to load the PATH in the as well. Can you guys try to see if it works for you?

Awesome, thank you!

For me it works if I launch vscode from the terminal using the command code. It seems that when we launch the vscode using the shortcut/icon it doesn't load the PATH or something like that, maybe it is not a bug of Claude, but they can try to load the PATH in the as well. Can you guys try to see if it works for you?

It worked this way!

In my case it Found version v12.22.9. Which was the stock version installed in my distro, I used nvm to switch to v20. I think it doesn't support nvm and jumps to stock version instead

<img width="813" height="750" alt="Image" src="https://github.com/user-attachments/assets/db42eb7a-9208-4ceb-ba94-bbe10db03a4b" />

Symptom
=======

Claude Code VS Code extension does not work, display error Error: Claude Code requires Node.js version 18 or higher to be installed..

On integrated terminal, it works.

And it also worked before 2.x.

Background
==========

I'm managing node.js via fnm. (On Windows)
And fnm does set PATH by profile file.

I guess, due to VS Code itself does not run profile code, (integrated terminal does) so PATH does not edited and passed to extension.

If CC 1.x did work based on system terminal, that can be reason it used to work.

So, how can I set node.js path for CC extension?

The same.

Same here, Windows machine,
NodeJs 22.20.0 LTS

Just updated Vscode and it seems to have fixed it. I had ASDF and the correct node version was already in the ~/.tool-versions file

This what works for me

Environment:

• Windows 11 with WSL2
• Cursor or VS Code running on Windows, project located in WSL2 filesystem
• Node.js installed in WSL2 only using "NVM" --> Claude Code extension won't pickup the proper node version that is set by NVM when you open the VS Code or Cursor.

Temporary Solution

• Add below code to ~/.bash_profile instead of ~/.bashrc

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

This way when you start VS Code or Cursor to load your project (w/c is located in WSL). IT will immediately pickup the proper node version that is set by NVM

Same problem. Was working fine. Upgrade to 2.0, stopped working with the same error

Found the (temporary fix):

<img width="791" height="302" alt="Image" src="https://github.com/user-attachments/assets/0c7d4cbd-f69e-4bb4-8cde-c56a530ecbe2" />

Same here, Windows 11, NodeJs v24.4.1 LTS

I had the same problem. I rolled back to 1.0.88 and everything works. The model seems more straightforward and efficient in this version.

Another work-around not requiring to downgrade is to go into the settings of the Claude Code extension and select the check-box for "Use-Terminal"

This will launch claude in a new terminal in your VS code terminal tab. Once that is run, then you can drag that specific terminal from the right-sidebar, up to any other pane.

What worked for me when using Cursor and nvm:

nvm use <my version with claude>
cursor .

Same Issue

• VS Code
• Cursor

node -v
v20.19.2

<img width="595" height="208" alt="Image" src="https://github.com/user-attachments/assets/6825f692-241d-4872-82c4-c3e1b0ac689e" />

Same for node v24.8.0

Fix is as suggested by @jonathanstiansen
In VS Code go to Code->Check for updates, it will restart and issue will not be there anymore.

Upgraded to node v24.9.0. Restarted my IDE, and it fixed the issue

Fix is as suggested by @jonathanstiansen In VS Code go to Code->Check for updates, it will restart and issue will not be there anymore.

somehow this worked, thanks

I believe the issue stems from the shell environment not resolving in time. If you get a warning in VSCode that it was unable to resolve your shell environment, then it is likely you will also face this warning in the claude code extension.

I am using zsh and I added zmodload zsh/zprof to the top and zprof to the bottom of my zsh config file to print out stats on shell start up and identified nvm was taking up 80% of the startup time. I lazy load nvm now and the shell starts so much faster.
(Claude walked me through resolving this, of course 😛)

After doing this I have not encountered the issue again and vscode starts up faster now as well.

https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-fails

If you're using VSCode, the problem seems to derive from launching Claude using the bunghole icon.

<img width="28" height="28" alt="Image" src="https://github.com/user-attachments/assets/2dcf5e52-2eb0-4f90-9df1-30eb3a85b2fe" />

If you run it from the terminal using claude it will open without issues.

Found the (temporary fix): <img alt="Image" width="791" height="302" src="https://private-user-images.githubusercontent.com/233914500/496468828-0c7d4cbd-f69e-4bb4-8cde-c56a530ecbe2.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTk1OTM5ODUsIm5iZiI6MTc1OTU5MzY4NSwicGF0aCI6Ii8yMzM5MTQ1MDAvNDk2NDY4ODI4LTBjN2Q0Y2JkLWY2OWUtNGJiNC04Y2RlLWM1NmE1MzBlY2JlMi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMDA0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTAwNFQxNjAxMjVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kMzI2OGUyYWZiOWMzY2U2YzdlNjNiYTA2NjMwNzI4YWZhYmU2N2E1NGNjNmU1ZTZjZGRlNzM0ZDRmNmNhNzE2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.KApe5gjiEUdFNZcF7OcQPaiB8sPWs3GFtpsY-HJGnXo">

this worked for me as well

What @rizkiandrianto-nanovest said worked for me. Launch your IDE from the terminal

For my case, It worked after terminating and opening the VSCode again.

<img width="310" height="190" alt="Image" src="https://github.com/user-attachments/assets/3921a411-ff1b-4e36-9260-47557e04a6cc" />

this solves the issue on vscode if you are using nvm
https://github.com/anthropics/claude-code/issues/8757#issuecomment-3374751214

What worked for me when using Cursor and nvm: nvm use <my version with claude> cursor .

this one worked.

How did you uninstall claude?

From here -

<img width="656" height="460" alt="Image" src="https://github.com/user-attachments/assets/670d740f-f691-4cdc-8fa6-242a9b4219fd" />

Also later part you need to logout sometimes because it throws authentication error. To logout, use Cmd/Ctrl + Shift + P and authentic again for login.

<img width="595" height="221" alt="Image" src="https://github.com/user-attachments/assets/9610e5f5-4dbf-4e9c-bb5a-568946265227" />

with regards to what @paustint wrote:

I believe the issue stems from the shell environment not resolving in time. If you get a warning in VSCode that it was unable to resolve your shell environment, then it is likely you will also face this warning in the claude code extension.

This was exactly the reason in my case. Shell env wasn't correctly parsed. In addition to profiling and lazy loading, you can wrap expensive operations (e.g. setting up oh-my-zsh, auto-complete, etc) within the following condition:

# Init oh-my-zsh only if vscode is not resolving the environment
# see https://github.com/microsoft/vscode/blob/020dc65e0d3dd3072a7f5c4278461d30eb67f3c1/src/vs/platform/shell/node/shellEnv.ts#L116
if [[ -z "$VSCODE_RESOLVING_ENVIRONMENT" ]] ; then

   ...

fi

That also helps for cases where it isn't the timeout but some other output that breaks resolving the env.

Upgraded to node v24.9.0. Restarted my IDE, and it fixed the issue

Yes, Reload will not fix it, you have to restart the VScode.

is this not urgent enough? I don't know what claude team is doing

Cmd + Shift + P -> Shell Command: Install 'code' command in PATH -> Restart Visual Code
Worked for me

if anyone is fighting with this on neovim & asdf, my solution was to remove the prior version of node that I had claude installed with, reshim, and then install it with the current global version. not sure why this solved it.

I am using NVM and even though my default was node 20, Claude Code was trying to use a different version.

The tip that helped me was to launch VS code from a terminal which is using a valid version of node. In my case, I used the Mac Terminal, launched VS Code with the 'code' command. It works.

Just opened Claude Code extension inside VSCode (without any reinstall) and it seems to be fixed 🤔

Edit: I don't have node inside my project, I have natively installed Claude Code

It seems that v2.0.13 fixes the issue.

CLI was working fine and then I clicked the Claude icon and I saw this even though I'm on node v22.18.0. I saw that I had a VSCode update and after installing that it worked.

it's been fixed now, I'm on 2.0.14 version

Not working for remote tunnel.

This issue has been fixed for Macos, looking for it to be fixed for Windows with claude (2.0.14) runs in WSL2 (Ubuntu), and the source code is located in Windows (VS Code opens the files from /mnt/c/...)

Same issue on my setup.

Windows 11 with WSL2 (ubuntu updated)
VS Code 1.105.0 with Claude Code extension (Claude Code for VS Code)
Claude Code 2.0.14
node 18.19.1 (under WSL)

If I open VS Code from WSL (or if I connect VS code to WSL), the claude code extensions works correctly.
If I just open VS Code under Windows (without connect to WSL), I got the error "Error: Claude Code requires Node.js version 18 or higher to be installed."

I didn't add this problem with Claude Code 2.0.11, I can use directly the extension without connection VS code to WSL.

I have a solution for people who are on Windows and not using WSL. I had this same error and resolved it, here's how:

1. Ensure you have Node.js installed (obvious I know, but just to be thorough).
2. Install Claude-code CLI (unclear if this is necessary, but I did it anyway). You can do so (after you have node installed) via: npm install -g @anthropic-ai/claude-code
3. Once both of those are installed close any existing terminal session and any existing VSCode window.
4. Open a new terminal and type node --version to ensure you have a suitable version of node installed.
5. Run VSCode from the terminal by typing code. Once it's opened you can re-open the Claude extension and that error should be gone. If you get some error when you type code in the Windows terminal, you need to configure your path such that the VSCode binary can be found. I'll leave this up to you to figure out, super common and solvable.

I believe the root cause of this is related to (Claude's) inability to correctly find things in the path / environment if you don't launch via the terminal which sets some of these things up by virtue of how the windows terminal works.

Good luck, have fun :)

The problem seem to came from the nodejs path check when the extension start. If we are under windows (and claude code installed under the WSL), he didn't check the version of nodejs under WSL but under Windows.

So you're right, we need to update nodejs under Windows, even if it is not used by claude code

This worked for me

Steps:
Install Node.js v20 LTS using nvm (you already have nvm installed):

nvm install 20
nvm use 20
nvm alias default 20

Verify the installation:

node --version  # Should show v20.x.x
npm --version   # Should show npm 10.x.x

Reinstall Claude Code CLI (to ensure it uses the correct Node.js version):
npm uninstall -g @anthropic-ai/claude-code
npm install -g @anthropic-ai/claude-code

This is another solution: for Node.js version manager users

• https://github.com/anthropics/claude-code/issues/8757#issuecomment-3374751214

Version 2.0.30 now includes native Win x64 support, which should drop the node requirement there (native has been available for other platforms for a while now).

Claude Code no longer depends on NodeJS. https://code.claude.com/docs/en/overview

Still getting this error on vs code (mac os - Version: 1.106.0) when connecting to remote host host via SSH. Works on local folders without issue.

Today I've updated Claude Code (2.0.44), VSCode and Claude plugin and I got this error.
Claude code doesn't work now in VSCode, impossible to work.
I've restarted my PC but still the same issue.

same issue, Windows, VScode.

Still getting this error on vs code (mac os - Version: 1.106.0) when connecting to remote host host via SSH. Works on local folders without issue.

I also get the same issue while connected to ssh.. any solution my friend?

> Still getting this error on vs code (mac os - Version: 1.106.0) when connecting to remote host host via SSH. Works on local folders without issue. I also get the same issue while connected to ssh.. any solution my friend?

Install nodejs and npm on the remote host allowed the error to go away. I hope that Claude can resolve this to not rely on the server needing nodejs.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

See https://github.com/anthropics/claude-code/issues/11868 as well