[FEATURE] Add VSCode extension setting to specify custom Node path

Resolved 💬 6 comments Opened Oct 1, 2025 by lazytype Closed Jan 9, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The extension fails to start a Claude session if it can't find node on the $PATH.

Proposed Solution

Add an optional "claude-code.nodePath" setting that the extension prioritizes over $PATH.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Developer tools/SDK

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗