Git lookups are cached, and errors now say whether git is missing or just somewhere unsearchable.
What's wrong with this entry?
Repeated git invocations now share one cached probe rather than redoing the same two expensive lookups each time: locating the git executable on PATH, and computing a PATH with directories a cloud session can reach stripped out. When git is not found, the error now distinguishes git being absent entirely from git existing only in a directory Claude Code refuses to search.
- The cached values are the resolved git executable and the reduced PATH.
- The "only in a directory we refuse to search" case is flagged separately based on the stderr text differing from the plain not-found message.
gitExeOnPath
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Stale editor bridge connections are dropped instead of read
Both mention integration
-
v2.1.234
Git remote URLs can no longer smuggle a different host
Both mention integration
-
v2.1.236
Change detection ignores custom diff drivers and submodules
Both mention integration