{"version":"2.1.309","anchor":"shell-parser-handles-and","canonical_anchor":"shell-parser-handles-and","heading":"Command checks now understand $'...' quoting and $$","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/shell-parser-handles-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Command checks now understand $'...' quoting and $$\n\nClaude Code's shell command reader now treats $'...' as a quoted string and handles $$ specially when checking commands\n\n**Unclear.** It is not clear whether seeing `$$` makes a command more or less likely to need permission.\n\n**What**\n\nBefore running a shell command, Claude Code reads it to decide whether it needs your permission. That reader now understands two more pieces of shell syntax:\n\n- `$'...'`: treated as a quoted string, with backslash escapes inside it honoured. Before, only `\"` and `'` started a quote.\n\n- `$$`: now recognised and flagged.\n\n**Why**\n\nReading commands correctly matters for permission checks, since a misread command can be judged wrongly.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}