{"version":"2.1.304","anchor":"dangerous-rm-detection-for-mounted-drive-paths","canonical_anchor":"dangerous-rm-detection-for-mounted-drive-paths","heading":"Deleting files on a mounted drive is now flagged as dangerous","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/dangerous-rm-detection-for-mounted-drive-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Deleting files on a mounted drive is now flagged as dangerous\n\nClaude Code's dangerous rm and rmdir check now recognises mounted drive paths such as \/mnt, \/Volumes, \/media and \/run\/media\n\n**Unclear.** Whether a flagged command is blocked outright or only needs your approval is not stated.\n\n**What**\n\nClaude Code checks delete commands (`rm` and `rmdir`) before running them and flags dangerous ones. That check now recognises paths on mounted drives, meaning disks attached to the system, such as:\n\n- `\/mnt\/x`\n\n- `\/Volumes`\n\n- `\/media`\n\n- `\/run\/media`\n\nA match is reported as a dangerous operation \"on mounted drive path\".\n\n**Why**\n\nDeleting on an external or shared drive can remove data well outside your project, so these commands are now treated as dangerous.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}