Unclear The new checks depend on an internal switch whose default is not stated, so it is unclear whether they apply for every reader.
What
Before Claude runs a shell command, Claude Code checks whether it is safe to run without asking you. For git commands, that check now asks for approval in more cases:
git initandgit init-dbin a command.{}and~in arguments, which are treated as values only known when the command runs.- Config keys
init.templatedir,core.sharedrepository,help.autocorrectandalias.*.
Before, only core.worktree, include.*, includeif.*, protocol allow settings, and ssh command or git proxy settings were treated this way. The new checks sit behind an internal switch.
Why
Git settings like these can make git run other programs. Treating them as needing approval stops a command that looks harmless from running code without you being asked.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The new checks depend on an internal switch whose default is not stated, so it is unclear whether they apply for every reader.