{"version":"2.1.323","anchor":"destructive-command-block-message-points-to-full-path-rm","canonical_anchor":"destructive-command-block-message-points-to-full-path-rm","heading":"Blocked delete commands now ask for the full path to be written out","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/destructive-command-block-message-points-to-full-path-rm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Blocked delete commands now ask for the full path to be written out\n\nA blocked removal command now explains it was not run and asks for the full path instead of a variable or relative path\n\n**Unclear.** What exactly triggers this block, and whether it is switched on, is not clear.\n\n**What**\n\nWhen Claude Code blocks a removal command, its message now says \"This command was not run.\" and asks for the full path to be written in the command itself, not through a shell variable or a relative path. A command written that way then goes through the normal permission check, where you can allow or deny it.\n\n**Why**\n\nDeleting through a variable or relative path makes it hard to see what will actually be removed. Asking for the full path puts the real target in front of you before you approve it.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}