›_ Claude Code Issues
Claude Code Issues / #11868

[BUG] vs code extension version v2.0.44 fails to initialize with "Node.js version 18 required"

Resolved 💬 16 comments Opened Nov 18, 2025 by memorsolutions Closed Nov 21, 2025
💡 Likely answer: A maintainer (blois, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code vs code extension v2.0.44 fails to initialize in VS Code instances with a
Node.js version 18 or higher is required error.

What Should Happen?

The extension should initialize correctly without any error messages.

Error Messages/Logs

Messages displayed in vs code output window for Claude VSCode immediately upon starting vs code.

2025-11-18 07:28:57.410 [info] Claude code extension is now active?
2025-11-18 07:28:57.410 [info] MCP Server running on port 23219 (localhost only)
2025-11-18 07:29:02.555 [info] AuthManager initialized
2025-11-18 07:29:02.555 [info] Getting authentication status
2025-11-18 07:29:02.555 [info] OAuth tokens found in secure storage
2025-11-18 07:29:02.555 [info] Auth status: method=claudeai
2025-11-18 07:29:02.555 [info] Loading config cache by launching Claude...
2025-11-18 07:29:02.555 [error] Failed to load config cache: Error: Claude Code requires Node.js version 18 or higher to be installed.
2025-11-18 07:29:02.556 [warning] Failed to check review upsell banner: Error: Claude Code requires Node.js version 18 or higher to be installed.

Steps to Reproduce

  1. Install or auto-update to Claude Code v2.0.44
  2. Open a new VS Code window (any project type)
  3. Observe error in Output panel (View → Output → select "Claude Code")
  4. Extension fails to initialize, Claude Code features unavailable

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.0.43

Claude Code Version

v2.0.44

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

16 Comments

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/8757
  2. https://github.com/anthropics/claude-code/issues/8410
  3. https://github.com/anthropics/claude-code/issues/8439

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

VirtualMaestro · 8 months ago

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.

memorsolutions · 8 months ago

Before closing this issue, please verify that the error I reported is not a regression from fixes made to the earlier issues.

xiaoxuanren · 8 months ago

I'm having same issue here! Windows, VScode.

blois collaborator · 8 months ago

Can folks confirm what architecture their Windows machine is running- is this x86 or arm?

We are still publishing a Win x86 extension which does not require node, but it looks like VSCode is picking up the universal extension for some reason. Investigating.

memorsolutions · 8 months ago

Mine is x86-64

xiaoxuanren · 8 months ago
Can folks confirm what architecture their Windows machine is running- is this x86 or arm? We are still publishing a Win x86 extension which does not require node, but it looks like VSCode is picking up the universal extension for some reason. Investigating.

Mine is x86-64

blois collaborator · 8 months ago

Still investigating. I was able to get back onto the correct track by uninstalling the extension, deleting ~\.vscode\extensions\anthropic.claude-code-2.0.44, then re-installing.

blois collaborator · 7 months ago

This appears to be https://github.com/microsoft/vscode/issues/276673

I can confirm that when downloading the platform-specific .vsix file from VSCode the resulting file, while named anthropic.claude-code-2.0.45-darwin-arm64.vsix is actually the universal package.

curl -O https://marketplace.visualstudio.com/_apis/public/gallery/publishers/anthropic/vsextensions/claude-code/2.0.45/vspackage?targetPlatform=darwin-arm64 downloads the correct version.

JELaVallee · 7 months ago

Can confirm from an Apple arm64 system that this worked on two systems:

  1. Uninstall the Claude Code extension from VS Code,
  2. Restart the VSC Extension engine (shift-cmd-P for it),
  3. Closing VS Code completely,
  4. Restart of VSC,
  5. Re-install of Claude Code,
  6. Re-setup of anthropic auth/api-key.
jdrickman · 7 months ago

I have this issue on Apple arm64, but only when connected to remote systems. The fix for me was to install the appropriate Node.js in the container the extension was installed and running in, so I sense this may be more of an awkwardly rolled out feature than a bug.

blois collaborator · 7 months ago

We've unpublished the universal package to prevent VSCode from mistakenly installing it.

crtag · 7 months ago

Not resolved on arm64 as a client using remote SSH amd64. WindowsARM -> SSH -> UbuntuAMD.
Regardless of node installation, version etc the extension still displays the same error message as above.
Using terminal claude version for now.

blois collaborator · 7 months ago

@crtag this should be picking up the appropriate linux architecture. Would be good to check that you are on a recent version on both Windows and Linux (such as 2.0.51 or newer). These builds should not have a node dependency at all- it's possible that something is causing VSCode to pick up an older extension version.

crtag · 7 months ago

@blois thank you. I trust this was the version issue my VSCode instance was trying to install. I went through a couple of cycles to install/uninstall the extension and it finally picked up Version 2.0.53 which finally landed everything in the right spot.

github-actions[bot] · 7 months ago

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.