Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Claude checks a checkout's git configuration before running git in it

You'll notice
Useful3 Signal3
Git Safety

Claude inspects a synced checkout's git config first and refuses to run git there if it looks unsafe.

What

Before running git in a synced directory, Claude Code now inspects that checkout's configuration and refuses when it looks unsafe, with a named reason. This blocks a repository from steering git commands run on your behalf.

Details
  • Refusal reasons include a git executable inside the checkout, a config file inside the work tree that contributes to configuration, include chains that are too deep or too numerous, non-UTF-8 hook or filter names, reftable or borrowed object stores, and a .git file pointing back inside the work tree.
  • It first probes the git binary to confirm it honours configuration from the environment, which requires git 2.31 or newer.
  • When it does run git, hooks are pinned off by name, filter drivers are cleared, and GIT_CONFIG and GIT_ATTR_SOURCE are blanked from the environment.
Evidence

[dirSync] refusing to run git in

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.

See this entry in the whole of v2.1.242 →