claude-code - 💡(How to fix) Fix [BUG] Claude Code Desktop MacOS can't find git , but git is installed [1 participants]

Install Git Git is required to run local sessions. Run xcode-select --install in Terminal to install the Command Line Tools, or download Git directly — or switch to a remote environment.

logs : 2026-04-29 20:10:01 [error] Git command failed: git --version { code: undefined, stderr: undefined, cwd: '/' } 2026-04-29 20:10:01 [error] [LocalSessionManager] Failed to check git status: Failed to spawn /Users/xxx/bin/git: spawn /Users/xxx/bin/git EACCES { stack: 'Error: Failed to spawn /Users/xxx/bin/git: spawn /Users/xxx/bin/git EACCES\n at ChildProcess.<anonymous> (/Applications/Claude.app/Contents/Resources/app.asar/.vite/build/index.js:296:13438)\n at ChildProcess.emit (node:events:521:24)\n at ChildProcess._handle.onexit (node:internal/child_process:293:12)\n at onErrorNT (node:internal/child_process:508:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21)' }

TL;DR

The issue is likely due to a permissions error when trying to spawn the git process, and a workaround could be to check the permissions of the git executable.

Guidance

• Verify the permissions of the git executable at /Users/xxx/bin/git to ensure it is executable by the user running Claude Code Desktop.
• Check the system logs for any related errors or warnings that may indicate a permission issue.
• Try running the command xcode-select --install in Terminal to install the Command Line Tools, as suggested by the error message, to see if it resolves the issue.
• Consider checking the PATH environment variable to ensure it includes the directory where the git executable is located.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue seems to be related to a regression in the latest version of Claude Code, and the error message suggests a permission issue when trying to spawn the git process.

Recommendation

Apply workaround: Check the permissions of the git executable and the PATH environment variable to ensure they are correct, as this is likely to resolve the issue without requiring an upgrade.