[BUG] "Git is required for local sessions" persists despite correct Git installation, CLAUDE_CODE_GIT_BASH_PATH, and gitBashPath in settings.json
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 desktop app on Windows shows "Git est requis pour les sessions locales"
("Git is required for local sessions") and blocks starting any local Code session,
despite Git being correctly installed and fully configured.
What Should Happen?
The desktop app should detect Git the same way the CLI does, or at
minimum should respect the gitBashPath value in settings.json when set.
Error Messages/Logs
Steps to Reproduce
- Confirmed
git --versionworks correctly in Git Bash - Set CLAUDE_CODE_GIT_BASH_PATH as a System environment variable
(not User) pointing to D:\Git\bin\bash.exe — confirmed correctly set
via echo %CLAUDE_CODE_GIT_BASH_PATH% in a fresh terminal
- Added the environment variable directly in the app's "Update local
environment" dialog (.env format)
- Also added "gitBashPath": "D:\\Git\\bin\\bash.exe" directly in
settings.json (%APPDATA%\Claude\.claude\settings.json) — no gitBashPath
key existed there by default
- Fully closed the app via system tray (not just the window) and
verified no Claude process remained running in Task Manager
- Fully restarted the PC
- Verified bash.exe exists at the exact path given
Despite all of the above, the error persists every time.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude Code version: 2.1.220
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
Using the Claude Code CLI directly (installed separately via irm https://claude.ai/install.ps1 | iex) works perfectly fine from the
same machine, in the same project folder (D:\Projet Claude), confirming
that Git itself and the Git Bash path are correctly set up system-wide.
The issue is isolated to the desktop app's Git detection specifically,
and is not resolved by setting gitBashPath in settings.json either,
which may be new information compared to prior similar reports.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗