{"version":"2.1.307","anchor":"dangerous-rm-check-now-fails-closed-on-nested-spans","canonical_anchor":"dangerous-rm-check-now-fails-closed-on-nested-spans","heading":"Complex shell commands may now ask before running when rm cannot be ruled out","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/dangerous-rm-check-now-fails-closed-on-nested-spans","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Complex shell commands may now ask before running when rm cannot be ruled out\n\nClaude Code now asks for approval when it cannot fully check nested parts of a command for a dangerous `rm`\n\n**What**\n\nClaude Code checks shell commands for a dangerous `rm` (the command that deletes files). Some commands contain other commands inside them. When Claude Code cannot check all of those inner pieces, it now asks for your approval instead of letting the command through.\n\nFor commands with more than 64 of these inner pieces, it now blocks whenever a further test matches, not only when `rm` appears in the text. The reasons it gives now start with \"not ruled out\".\n\n**Why**\n\nSome complicated commands that used to run without asking will now stop for your approval, because Claude Code could not show they were safe.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}