{"version":"2.1.238","anchor":"bash-safety-refusals-now-tell-you-what-to-do-instead","canonical_anchor":"bash-safety-refusals-now-tell-you-what-to-do-instead","heading":"Bash safety refusals now tell you what to do instead","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/bash-safety-refusals-now-tell-you-what-to-do-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Bash safety refusals now tell you what to do instead\n\nBlocked bash commands now add a next step, naming the directory to run the command from.\n\n**What**\n\nTwo refusals gained a second sentence with an actionable next step. When a wrapper script is placed before a git command, and when `env` is used with flags Claude Code does not model, the message now names the working directory to run the command from.\n\n**Details**\n\n- Only the message text changed; the same commands are still refused.\n\n**Evidence**\n\n`Run the command without that env flag from `\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}