{"version":"2.1.265","anchor":"bash-command-permission-dry-run-check-simplified-to-a-single","canonical_anchor":"bash-command-permission-dry-run-check-simplified-to-a-single","heading":"Bash command permission dry-run check simplified to a single flag","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-command-permission-dry-run-check-simplified-to-a-single","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash command permission dry-run check simplified to a single flag\n\nA bash command permission check during streaming execution now relies on a single flag instead of two conditions\n\n**Unclear.** What behavior difference, if any, this produces for users is not stated in the finding.\n\n**What**\n\nA guard used while checking bash command permissions during streaming execution used to bail out only when both a local flag and a `notRunning()` check agreed; it now bails out based on the local flag alone.\n\n**Why**\n\nThe finding doesn't explain the practical effect, but simplifying two conditions into one suggests the `notRunning()` check was found redundant for this particular guard.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}