{"version":"2.1.311","anchor":"dangerous-removal-permission-rule-becomes-waivable-in-bypass","canonical_anchor":"dangerous-removal-permission-rule-becomes-waivable-in-bypass","heading":"Dangerous-removal permission rule marked as waivable in bypass mode","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/dangerous-removal-permission-rule-becomes-waivable-in-bypass","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Dangerous-removal permission rule marked as waivable in bypass mode\n\nThe permission rule for dangerous removals is now marked as waivable in bypass-permissions mode while staying marked as immune to it\n\n**Unclear.** It is not known what reads the new waivable marking, so whether dangerous removals are now allowed in bypass mode is unclear.\n\n**What**\n\nBypass-permissions mode lets Claude Code act without asking you first. The permission rule covering dangerous removals (deleting files in risky ways) was marked as immune to that mode. It is now also marked as waivable in that mode.\n\n**Why**\n\nThis could loosen how dangerous removals are treated when you run in bypass-permissions mode.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}