{"version":"2.1.311","anchor":"dangerous-rm-checks-can-be-waived-by-claude-code-even-more-d","canonical_anchor":"dangerous-rm-checks-can-be-waived-by-claude-code-even-more-d","heading":"CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS lets dangerous rm skip prompts","tier":"use","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/dangerous-rm-checks-can-be-waived-by-claude-code-even-more-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### `CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS` lets dangerous rm skip prompts\n\nSetting CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS lets dangerous rm commands run without a prompt in bypass permissions mode\n\n**What**\n\nA new environment variable, `CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS`, removes the prompt Claude Code shows before running a dangerous `rm` command, the shell command that deletes files. An environment variable is a named value set in your terminal before Claude Code starts. It only has an effect in bypass permissions mode, the mode where Claude Code runs tools without asking you first.\n\nEven then, it only takes effect once managed settings (settings your organization sets for you) and plugin hooks have finished loading, and only when several checks pass, including these:\n\n- No read-block rules or deny rules are set\n\n- No settings changes are still waiting to be applied\n\n- The managed settings were read without problems\n\nIt does nothing in sessions started by another Claude Code session. On Windows, if Claude Code cannot read the registry (the store where Windows keeps system settings), the session reports that the variable has no effect. When the variable is set, Claude Code shows this warning:\n\nCLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS is set, so dangerous rm commands can run without a prompt in bypass permissions mode once managed settings and plugin hooks have loaded. If you didn't set it, check your shell profile.\n\n**Why**\n\nThis turns off a safety check that normally stops files from being deleted without your say. If you see the warning and did not set the variable yourself, look in your shell profile, the file your terminal runs each time it starts, and remove it from there.\n\n- Area: Permissions\n- Names: `CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}