{"version":"2.1.290","anchor":"shell-parser-prefixed-special-variable-subscript-and","canonical_anchor":"shell-parser-prefixed-special-variable-subscript-and","heading":"More shell commands using $$ now ask for permission","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-parser-prefixed-special-variable-subscript-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### More shell commands using `$$` now ask for permission\n\nShell commands using patterns like `$$[` are now treated as too complex to judge and prompt for permission\n\n**Unclear.** The exact commands that now prompt when they did not before are not fully stated.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to decide whether it is safe to run without asking. Its reader now treats `$` as a special variable name when checking subscripts. As a result, commands with patterns such as `$$[` or `$$:x` are judged too complex to read and lead to a permission prompt.\n\nThe message shown when the reader cannot follow a `${ ...; }` command substitution is also shorter. A command substitution runs a command and uses its output in place.\n\n**Why**\n\nCommands using these patterns that used to run without asking may now stop and ask for your approval first.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}