{"version":"2.1.317","anchor":"bash-parser-flags-operand-diffs-under-a-new-condition","canonical_anchor":"bash-parser-flags-operand-diffs-under-a-new-condition","heading":"Some shell commands using $ values are now treated as unreadable","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/bash-parser-flags-operand-diffs-under-a-new-condition","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Some shell commands using `$` values are now treated as unreadable\n\nThe shell-command reader now rejects more commands that contain `$` values, so those commands will ask for permission\n\n**Unclear.** Which commands the new check matches is not clear.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to work out what it does. It now runs an extra check on commands that contain `$` values (shell variables and similar). When the check matches, Claude Code treats the command as one it cannot read reliably.\n\n**Why**\n\nA command Claude Code cannot read reliably needs your permission before it runs, so you may see more permission prompts for some commands.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}