[BUG] `requires git-bash` error persists on Windows even when `CLAUDE_CODE_GIT_BASH_PATH` and symlink are set

Resolved 💬 6 comments Opened Dec 6, 2025 by cafrecio Closed Feb 14, 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?

The Claude Code VS Code extension (versions newer than 1.0.126) fails to detect Git Bash on Windows, despite the environment being fully configured. It continuously shows the "requires git-bash" error, making the extension unusable. We have attempted all known community workarounds, but the issue persists, indicating a fundamental regression in the detection logic introduced after version 1.0.126.

What Should Happen?

The Claude Code panel should detect Git Bash based on the CLAUDE_CODE_GIT_BASH_PATH environment variable and start accepting prompts.

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

Steps to Reproduce

  1. Install Claude Code VS Code extension (any version > 1.0.126).
  2. Install Git Bash (e.g., v2.51.2.windows.1).
  3. Set Windows Environment Variable CLAUDE_CODE_GIT_BASH_PATH to the correct path (e.g., C:\Program Files\Git\bin\bash.exe).
  4. Reboot the PC to ensure variables are loaded.
  5. Open VS Code and open the Claude Code panel.

(The error appears immediately, preventing usage.)

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.0.126

Claude Code Version

1.0.126

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

  • The issue is a regression that started after version 1.0.126.
  • We have exhaustively attempted all configuration workarounds, including setting system PATH, setting the variable in both User and System scopes, and setting the VS Code integrated shell ("terminal.integrated.shell.windows").
  • Failed Workaround (Symlink): We also created a symbolic link (mklink /D C:\GitBash "C:\Program Files\Git") and pointed the environment variable to the simplified path (C:\GitBash\bin\bash.exe), but the error still persists. This strongly suggests the bug is in the internal detection method used by the extension code itself.

View original on GitHub ↗

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