{"version":"2.1.307","anchor":"new-safe-gate-checks-on-bash-parsing-glob-matched-git-names","canonical_anchor":"new-safe-gate-checks-on-bash-parsing-glob-matched-git-names","heading":"Two server-controlled checks tighten how shell commands are judged safe","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/new-safe-gate-checks-on-bash-parsing-glob-matched-git-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Two server-controlled checks tighten how shell commands are judged safe\n\nTwo new server-controlled checks change how git command names are matched and add a stricter test for sed commands\n\n**Unclear.** Whether these checks are active, and whether they change which commands run without asking, is not established.\n\n**What**\n\nBefore running a shell command, Claude Code checks whether it is safe enough to run without asking you. Two new switches, set from Anthropic's servers, change parts of that check:\n\n- Git command names: a wildcard pattern is turned into an exact matching rule and tested against the names of git programs.\n\n- `sed` commands: a second pattern is added to the check, and the message shown when a command is refused gains extra wording.\n\nA third change affects how command options are judged safe. Before, the single `sed` pattern and the older option check always applied.\n\n**Why**\n\nThis looks like the shell checker being hardened step by step. Depending on how the switches are set, some commands that used to run without asking may now need your approval.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}