Source Intelligence

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.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

Every git command now runs with hooks, filesystem monitors and prompt helpers disabled

You'll notice
Useful3 Signal3
Git Safety not in their notes

Every git command Claude runs now has hooks, filesystem monitors and prompt helpers turned off.

protocol.ext.allowcore.fsmonitorcore.askPassGIT_PROXY_COMMAND
What

All git invocations go through one wrapper that pins a fixed set of config so a repository cannot make git run its own programs. Hooks are pointed at the null device, protocol.ext.allow is set to never, submodule recursion and signature display are off, core.fsmonitor and core.askPass are neutralized, and GIT_PROXY_COMMAND is blanked. Callers that deliberately want repo hooks can opt back in.

Details
  • core.hooksPath is forced to /dev/null, or \\.\NUL on Windows, and a caller-supplied hooks path is rewritten back to the null device.
  • An allowRepoGitHooks option drops the hooks, askPass and submodule entries for the few call sites that want repo behaviour.
  • Previously this module only carried the GIT_TERMINAL_PROMPT/GIT_ASKPASS/GCM_INTERACTIVE environment settings and the ssh BatchMode arguments.
Evidence

protocol.ext.allow

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.247 →