{"version":"2.1.273","anchor":"bash-permission-checks-new-fallback-path-when-a-classifier","canonical_anchor":"bash-permission-checks-new-fallback-path-when-a-classifier","heading":"Bash permission checks: new fallback path when a classifier-based 'ask' isn't overridable","tier":"internal","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bash-permission-checks-new-fallback-path-when-a-classifier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bash permission checks: new fallback path when a classifier-based 'ask' isn't overridable\n\nBash safety checks gained a subcommand-based fallback when an 'ask' decision from the classifier can't be overridden\n\n**What**\n\nWhen Claude Code's safety-check classifier decides a bash command should prompt you with 'ask' and that decision isn't one that can simply be approved by the classifier, Claude Code now runs an extra check on the decision's reason and, where applicable, tries a new fallback that looks at the command's individual subcommands before falling back to the original 'ask' decision. The separate logic for always asking about certain subcommands was also consolidated into one shared piece of code.\n\n**Why**\n\nThis adds another layer of analysis before Claude Code settles on asking you for permission to run a bash command, aiming to make that decision more precise.\n\n- Area: Bash Safety\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}