{"version":"2.1.310","anchor":"shell-parser-gets-a-quotedbackslashkept-option","canonical_anchor":"shell-parser-gets-a-quotedbackslashkept-option","heading":"Shell command reader gains a setting for backslashes inside quotes","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/shell-parser-gets-a-quotedbackslashkept-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Shell command reader gains a setting for backslashes inside quotes\n\nThe part of Claude Code that reads shell commands for permission checks can now be told how to treat backslashes inside quotes\n\n**What**\n\nBefore running a shell command, Claude Code breaks it into parts to check it against your permission rules. That reader now has an option that controls whether a backslash inside quotes is kept as written. The option is on unless something explicitly turns it off, and it carries over into commands nested inside the main one, such as text inside `$( )`.\n\n**Why**\n\nThis matters only in edge cases where a command uses backslashes inside quotes. With the option left at its default, backslashes inside quotes are kept.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}