[DOCS] Settings reference missing `skipDangerousModePermissionPrompt` property

Resolved 💬 5 comments Opened Feb 17, 2026 by coygeek Closed Apr 28, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

"Settings properties" table and the Permissions page's "Permission modes" section

Current Documentation

The Settings page (settings.md) documents these permission-related properties:

| Property | Description |
|----------|-------------|
| defaultMode | Default permission mode when opening Claude Code |
| disableBypassPermissionsMode | Set to "disable" to prevent bypassPermissions mode from being activated |

The Permissions page (permissions.md) documents:

  • The bypassPermissions permission mode
  • The --dangerously-skip-permissions CLI flag
  • The disableBypassPermissionsMode managed setting

Neither page mentions skipDangerousModePermissionPrompt.

What's Wrong or Missing?

When a user launches Claude Code with --dangerously-skip-permissions or sets defaultMode to bypassPermissions, Claude Code displays a one-time warning prompt asking the user to confirm they understand the risks. When the user accepts this prompt, Claude Code automatically writes "skipDangerousModePermissionPrompt": true to the user-level settings.json (~/.claude/settings.json). On subsequent launches, this setting suppresses the warning prompt so the user is not asked again.

This setting is completely undocumented:

  1. Settings reference (settings.md) — The settings properties table has no entry for skipDangerousModePermissionPrompt
  2. Permissions page (permissions.md) — The bypassPermissions mode section does not mention that accepting the warning prompt writes a persistent setting, nor how to reset it
  3. CLI reference — The --dangerously-skip-permissions flag documentation does not mention the one-time prompt or the resulting setting

Users who find this setting in their settings.json have no way to understand what it does, where it came from, or whether it is safe to modify. Removing it causes the bypass permissions warning prompt to reappear on next launch (which is the expected reset behavior, but this is also undocumented).

Suggested Improvement

  1. Add skipDangerousModePermissionPrompt to the settings properties table in settings.md:

| Property | Description | Example |
|----------|-------------|---------|
| skipDangerousModePermissionPrompt | When true, suppresses the one-time safety warning shown when bypassPermissions mode is activated. Automatically set by Claude Code when the user accepts the warning prompt. Remove this setting to see the warning again. | true |

  1. In the bypassPermissions section of permissions.md, add a note explaining the one-time warning prompt behavior:
When bypassPermissions mode is first activated (via defaultMode or --dangerously-skip-permissions), Claude Code displays a safety warning prompt. Accepting the prompt writes skipDangerousModePermissionPrompt: true to your user settings, suppressing the warning on future launches. To re-enable the warning, remove this setting from ~/.claude/settings.json.

Impact

Medium - Makes feature difficult to understand

Additional Context

  • Observed in Claude Code v2.1.44
  • The setting is written to user-level settings only (~/.claude/settings.json), not project-level
  • Tested behavior: removing the setting from settings.json causes the bypass permissions warning to reappear on the next interactive launch, and accepting the warning re-adds the setting automatically
  • The --dangerously-skip-permissions flag in non-interactive mode (claude -p) does not trigger the warning prompt, so the setting is only relevant for interactive sessions
  • Related documented setting: disableBypassPermissionsMode (which prevents bypassPermissions mode entirely) is documented — but the complementary skipDangerousModePermissionPrompt (which controls the warning prompt within that mode) is not

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗