{"version":"2.1.304","anchor":"rm-prompt-for-mounted-drives-and-drive-root-targets","canonical_anchor":"rm-prompt-for-mounted-drives-and-drive-root-targets","heading":"rm on a mounted drive or a drive's top level now needs your approval","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/rm-prompt-for-mounted-drives-and-drive-root-targets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### `rm` on a mounted drive or a drive's top level now needs your approval\n\nClaude Code now asks before `rm` removes a mounted drive, its parent folder or a top-level item on a drive; an environment variable turns this off\n\n**Unclear.** Exactly which paths count as a mounted drive, and whether the check runs outside Windows and WSL, is not stated.\n\n**What**\n\nClaude Code now asks for your approval before running `rm` (the command that deletes files) when it would remove:\n\n- a mounted drive\n\n- the folder that holds mounted drives\n\n- a file or folder at the top level of a drive\n\n- files picked out by a recursive delete whose pattern Claude Code cannot read\n\nThis approval cannot be granted ahead of time by your permission rules. To turn the prompt off, set the environment variable `CLAUDE_CODE_DISABLE_MOUNTED_DRIVE_RM_PROMPT`.\n\n**Why**\n\nThe prompt is on by default, so deleting on a mounted drive now stops and waits for you, which guards against wiping a whole drive by mistake.\n\n- Flag `tengu_iridescent_boot`: Not enough to say (read for one account on one subscription tier against v2.1.304; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}