{"version":"2.1.323","anchor":"bash-command-parser-flags-more-misreadings","canonical_anchor":"bash-command-parser-flags-more-misreadings","heading":"Shell command checks flag more tricky command patterns","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bash-command-parser-flags-more-misreadings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Shell command checks flag more tricky command patterns\n\nClaude Code's shell command checker now flags more patterns it may misread and has a time limit on its work\n\n**Unclear.** It is not clear what these flags change in practice, or which of them are switched on.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to judge whether it is safe. That reader now flags more patterns it might misread:\n\n- Bracket words.\n\n- Brace expansion edge cases.\n\n- `=` inside a `[[ ]]` test.\n\n- `#` inside a `[[ ]]` test.\n\n- Digits right before a redirect, such as `2>`.\n\nIt also now has a CPU time limit and caps on how long substituted variable text can grow. Some of these flags appear to depend on an internal switch.\n\n**Why**\n\nThe command safety check is harder to fool. More commands may be treated as too complex to allow automatically, so you may be asked about them.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}