{"version":"2.1.307","anchor":"shell-parser-zsh-brace-diff-flag-and-unparsed-body-overrun","canonical_anchor":"shell-parser-zsh-brace-diff-flag-and-unparsed-body-overrun","heading":"Stricter checks on quoted text when Claude Code analyzes shell commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/shell-parser-zsh-brace-diff-flag-and-unparsed-body-overrun","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Stricter checks on quoted text when Claude Code analyzes shell commands\n\nClaude Code's shell command analysis now flags quoted text containing backticks, certain $ forms or escaped quotes, which zsh may read differently\n\n**What**\n\nBefore running a shell command, Claude Code reads it to work out what it does and which permissions it needs. That reading now marks quoted text that contains a backtick, a `$` followed by `{`, `(` or `[`, or an escaped quote, because zsh may treat it differently. Before, quoted text was skipped without these checks. In some cases the analysis can now give up on part of a command it could not fully read.\n\n**Why**\n\nIt makes the permission checks on shell commands stricter.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}