CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS
Updated by Alex Sorokoletov
CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS is a Claude Code environment variable: When set, dangerous rm commands can run without a confirmation prompt in bypass permissions mode. The build carries guards where it has no effect: in a session without managed settings, or on Windows while the registry cannot be read for managed settings, dangerous rm commands keep their usual checks. Added in v2.1.311 and still present in v2.1.311. It is listed in the official reference.
| Status | Present in v2.1.311 |
|---|---|
| Added | Added in v2.1.311 |
| Category | Permissions and sandbox |
| Official docs | Listed |
How to set it
For one session, export it in the shell that starts Claude Code:
export CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS=<value>
claudeTo apply it to every session, add it to the env object of a settings file:
// ~/.claude/settings.json
{
"env": {
"CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS": "<value>"
}
}Release notes that mention it
- Claude Code Version Tracker: Undocumented Env Vars, Feature Gates & Models
- claude-code-env-vars-v2-1-311
Related variables
CLAUDE_CODE_AUTO_MODE_EXTERNAL_PERMISSIONS: Hands permission decisions to an external policy engine instead of the built-in prompt.CLAUDE_CHROME_PERMISSION_MODE: Permission mode for Claude for Chrome.CLAUDE_CODE_AUTO_MODE_CLASSIFY_EDITS: Turns the classification pass on: every edit runs through the classifier before it touches disk.CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL: Governs whether Auto mode may delete content as part of an edit.CLAUDE_CODE_AUTO_MODE_EDIT_REMOVAL_CAP: Caps how much a single autonomous edit can remove before it's held for a human.CLAUDE_CODE_AUTO_MODE_GIT_STATUS: Feeds the working tree's git status into the classifier's context.CLAUDE_CODE_AUTO_MODE_GIT_STATUS_LIMIT: Bounds how much of that status is included, so the classifier prompt doesn't balloon in large or messy repos.CLAUDE_CODE_AUTO_MODE_GIT_STATUS_UPLOADS: Controls whether git-status context is uploaded to the classification service.
Frequently asked questions
What does CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS do?
When set, dangerous rm commands can run without a confirmation prompt in bypass permissions mode. The build carries guards where it has no effect: in a session without managed settings, or on Windows while the registry cannot be read for managed settings, dangerous rm commands keep their usual checks.
Which Claude Code version has CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS?
Added in v2.1.311 and still present in v2.1.311.
How do I set CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS?
Export it before starting Claude Code (export CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS=value), or add it to the "env" object in ~/.claude/settings.json to apply it to every session.
All variables, searchable: Claude Code environment variables.