{"version":"2.1.312","anchor":"bash-permission-check-fails-closed-when-it-throws","canonical_anchor":"bash-permission-check-fails-closed-when-it-throws","heading":"A crashed safety check on a shell command now asks you instead of carrying on","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/bash-permission-check-fails-closed-when-it-throws","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### A crashed safety check on a shell command now asks you instead of carrying on\n\nIf Claude Code's permission check on a shell command fails partway, it now asks you rather than reusing an earlier decision\n\n**What**\n\nBefore Claude runs a shell command, Claude Code checks whether it is safe and whether it needs your permission. If that check fails with an error, Claude Code now asks you, with the note \"The permission check for this command did not finish, so its safety checks did not run.\" Before, it logged the error and returned whatever decision it had reached so far.\n\nWarnings about dangerous file deletion are also now kept when a command is too complex to analyse fully, and the way several decisions are combined now favours some outcomes differently.\n\n**Why**\n\nA failure inside the safety check now leads to a prompt instead of possibly letting the command run without one.\n\n- Flag `tengu_amber_larch`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.312; this account: on, anonymous baseline: on, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}