{"version":"2.1.273","anchor":"new-early-bail-out-for-over-complex-bash-commands-before-pre","canonical_anchor":"new-early-bail-out-for-over-complex-bash-commands-before-pre","heading":"New early bail-out for over-complex bash commands before prefix-rule matching","tier":"internal","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-early-bail-out-for-over-complex-bash-commands-before-pre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New early bail-out for over-complex bash commands before prefix-rule matching\n\nOverly complex bash commands now skip permission-rule matching entirely instead of being reasoned about\n\n**What**\n\nBefore Claude Code splits a bash command into subcommands to match it against permission rules, it now runs a new complexity-and-length check first. If the command trips this check, Claude Code stops and declines to reason about it further, rather than attempting to split and match it.\n\n**Why**\n\nThis avoids Claude Code trying to apply permission logic to bash commands too complex to analyze reliably, likely reducing the chance of a permission rule being matched incorrectly against a convoluted command.\n\n- Area: Bash Safety\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}