{"version":"2.1.271","anchor":"bash-tool-git-command-parsing-hardened-for-pathpermission-e","canonical_anchor":"bash-tool-git-command-parsing-hardened-for-pathpermission-e","heading":"Bash-tool git command parsing hardened for path\/permission extraction","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/bash-tool-git-command-parsing-hardened-for-pathpermission-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Bash-tool git command parsing hardened for path\/permission extraction\n\nBash-tool permission logic parses git commands more carefully before approving them\n\n**What**\n\nWhen Claude Code decides whether a `git` command in the Bash tool can be auto-approved, it now parses the command line more carefully. New internal helpers correctly:\n\n- split combined short options (like `-abc` meaning `-a -b -c`)\n\n- extract `--work-tree` and `-C` values, which change which directory a git command operates on\n\n- recognize glob bracket-expression syntax, including character classes with an embedded `]`\n\n- exclude commands that use `GIT_CONFIG` or other environment-based redirection, since those could make it unsafe to reason about the command just by looking at its text\n\n**Why**\n\nGit commands can change their target directory or configuration through options and environment variables in ways that are easy to misparse. Handling these cases correctly avoids auto-approving a git command whose real effect isn't what a simple text scan would suggest.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}