{"version":"2.1.319","anchor":"shell-parser-handles-escaped-double-quotes-and-newlines-in-b","canonical_anchor":"shell-parser-handles-escaped-double-quotes-and-newlines-in-b","heading":"Shell command parsing now treats escaped quotes and line breaks like other escapes","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/shell-parser-handles-escaped-double-quotes-and-newlines-in-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Shell command parsing now treats escaped quotes and line breaks like other escapes\n\nWhen reading shell commands, Claude Code now treats a backslash before a double quote or a line break the same as before a backtick, `$` or backslash\n\n**What**\n\nClaude Code reads shell commands to understand them before running them. A backslash followed by a double quote or a line break is now handled the same way as a backslash followed by a backtick, `$` or another backslash. Before, only those last three were handled.\n\n**Why**\n\nThis could change how some commands are analysed when Claude Code decides whether they need your permission.\n\n- Area: Bash Safety\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}