{"version":"2.1.273","anchor":"bash-commands-too-complex-for-ast-analysis-now-get-blocked-o","canonical_anchor":"bash-commands-too-complex-for-ast-analysis-now-get-blocked-o","heading":"Bash commands too complex for AST analysis now get blocked outright under the read-block setting","tier":"notice","area":"Bash Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bash-commands-too-complex-for-ast-analysis-now-get-blocked-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bash commands too complex for AST analysis now get blocked outright under the read-block setting\n\nBash commands too complicated to analyze are now blocked outright when reads are locked to the working directory\n\n**What**\n\nWhen the `permissions.blockReadsOutsideWorkingDirectories` setting is turned on (which makes Claude Code's file tools refuse reads outside the working directory), Bash commands that are too structurally complex for Claude Code to analyze are now refused outright with a hard \"ask\" prompt, unless a specific exemption applies. Previously, these overly complex commands fell through to the normal complexity-based approval flow instead.\n\n**Why**\n\nCommands too complex to analyze can't be reliably checked against the read-location block, so Claude Code now asks for explicit approval on them rather than risking one slipping through unchecked.\n\n- Area: Bash Safety\n- Names: `blockReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}