[BUG] Visual Studio Code extension - $PATH variable is not loaded to bash tool invocations

Resolved 💬 8 comments Opened Jan 29, 2026 by afestupinanp Closed Mar 6, 2026

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?

Whenever the bash tool starts a new shell, it does so without the existing $PATH variable, which gets annoying really quick because for each tool call, it has to reconfigure the path, so for devs that are using virtual envs or nvm they must reconfigure or do workarounds.

This is not an issue when running Claude Code from the CLI, which does load the $PATH correctly on each bash tool call invocation.

What Should Happen?

The $PATH should be loaded from the existing terminal profile configuration, or the existing $PATH which the process was started with.

Error Messages/Logs

Steps to Reproduce

  1. Start Visual Studio Code with the extension installed
  2. Ask to print out the $PATH variable.
  3. Result is a completely different $PATH

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.23

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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