{"version":"2.1.319","anchor":"bash-parser-handles-backtickescape-unsupported-nodes-more-f","canonical_anchor":"bash-parser-handles-backtickescape-unsupported-nodes-more-f","heading":"Commands hidden inside escaped backticks are now checked for permissions","tier":"notice","area":"Bash Safety","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-parser-handles-backtickescape-unsupported-nodes-more-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Commands hidden inside escaped backticks are now checked for permissions\n\nClaude Code now re-reads the inside of certain escaped-backtick parts of a shell command so its permission checks see the commands there\n\n**What**\n\nBefore running a shell command, Claude Code breaks it into its parts to see which programs it would run, so it can apply your permission rules (the settings that decide what Claude may run without asking). Some commands contain backtick sections with escaping that the parser cannot handle directly. Claude Code now re-reads the inside of those sections as a command of its own, with a limit on how much work it will do. Before, it only stepped through them without re-reading.\n\n**Why**\n\nThis closes a gap where a command tucked inside escaped backticks could slip past the permission and command checks.\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"}