[BUG]

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 doesn't detect Git Bash on Windows when WSL bash.exe is present in System32. CLAUDE_CODE_GIT_BASH_PATH and claudeCode.gitBashPath settings are ignored. C:\Windows\System32\bash.exe always takes priority over C:\Program Files\Git\bin\bash.exe"

What Should Happen?

"Claude Code VS Code extension doesn't detect Git Bash on Windows when WSL bash.exe is present in System32. CLAUDE_CODE_GIT_BASH_PATH and claudeCode.gitBashPath settings are ignored. C:\Windows\System32\bash.exe always takes priority over C:\Program Files\Git\bin\bash.exe"

Error Messages/Logs

Error: Claude Code on Windows requires git-bash (https://git-scm.com/downloads/win). If installed but not in PATH, set environment variable pointing to your bash.exe, similar to: CLAUDE_CODE_GIT_BASH_PATH=C:\Program Files\Git\bin\bash.exe
View output logs · Troubleshooting resources

Steps to Reproduce

"Claude Code VS Code extension doesn't detect Git Bash on Windows when WSL bash.exe is present in System32. CLAUDE_CODE_GIT_BASH_PATH and claudeCode.gitBashPath settings are ignored. C:\Windows\System32\bash.exe always takes priority over C:\Program Files\Git\bin\bash.exe"

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

last and old 2.1.7

Platform

Anthropic API

Operating System

Environnement :

Windows 11 avec WSL installé
Claude Code v2.1.80
Extension VS Code v2.1.7 et v2.1.79 (toutes les versions testées)
Git for Windows v2.53.0 installé dans C:\Program Files\Git

Ce qui a été essayé sans succès :

claudeCode.gitBashPath dans settings.json
Variable CLAUDE_CODE_GIT_BASH_PATH en User et Machine
Ajout de C:\Program Files\Git\bin en premier dans le PATH système
terminal.integrated.env.windows dans settings.json

Cause probable :

C:\Windows\System32\bash.exe (WSL) est toujours prioritaire
L'extension ignore toutes les configurations alternatives

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_