{"version":"2.1.317","anchor":"new-bot-protected-gates-and-makeawkgit-exec-path-checks","canonical_anchor":"new-bot-protected-gates-and-makeawkgit-exec-path-checks","heading":"New refusal reasons for make, awk and git commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-bot-protected-gates-and-makeawkgit-exec-path-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### New refusal reasons for make, awk and git commands\n\nClaude Code can now refuse commands because a makefile or awk script cannot be checked, or because of where git looks for its programs\n\n**Unclear.** It is not clear whether these refusals are active or what switches them on.\n\n**What**\n\nClaude Code checks shell commands before running them. It has new reasons for refusing one:\n\n- a makefile cannot be checked\n\n- an awk script cannot be checked, so what awk would run from it is unknown\n\n- git runs with its program folder (its exec path) set inside the folder Claude Code started in\n\n- git's exec path cannot be confirmed as a full, absolute path\n\nThese arrive alongside several new remote switches.\n\n**Why**\n\nThese are likely stricter permission checks on `make`, `awk` and `git` commands.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}