{"version":"2.1.310","anchor":"git-command-check-argv0-env-now-rejected-with-a-specific-me","canonical_anchor":"git-command-check-argv0-env-now-rejected-with-a-specific-me","heading":"Git safety check now refuses commands that set ARGV0, with its own message","tier":"notice","area":"Git","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/git-command-check-argv0-env-now-rejected-with-a-specific-me","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Git safety check now refuses commands that set ARGV0, with its own message\n\nClaude Code's git write protection now refuses a command that sets ARGV0 and explains that it changes the name git is started under\n\n**What**\n\nClaude Code checks git commands before running them, to protect against git writing where it should not. `ARGV0` is an environment variable, a named value passed to a program when it starts, and it changes the name a program is started under.\n\nWhen a git command sets `ARGV0`, the check now refuses it with a specific message. The message says that `ARGV0` changes the name git is started under, so the git subcommand that would run cannot be verified. Before, such a command only got a general message about environment settings Claude Code could not inspect.\n\n**Why**\n\nIf git could be started under a different name, Claude Code could not be sure which git action was actually going to run. Refusing these commands closes a way around the git write protection, and the new message tells you exactly why the command was stopped.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}