--dangerously-skip-permissions still prompts for Edit/Write tool confirmations

Status Fixed / completed
Reported on v2.1.90
Maintainer reply ✓ Yes — ashwin-ant
Activity 5 comments · opened Apr 2, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator) responded on this thread — see the highlighted reply below.

Description

When running Claude Code with --dangerously-skip-permissions, the Edit and Write tools still show a confirmation prompt:

Do you want to make this edit to file.py?
 ❯ 1. Yes
   2. Yes, allow all edits during this session (shift+tab)
   3. No

This prompt appears on every edit until the user selects option 2 ("allow all edits during this session"), which only persists for the current session.

Expected Behavior

--dangerously-skip-permissions should bypass all permission checks, including Edit/Write confirmations. The CLI help text describes it as: "Bypass all permission checks."

Reproduction

claude --dangerously-skip-permissions
# Then ask Claude to edit any file — it will prompt for confirmation

Environment

  • Claude Code version: 2.1.90
  • OS: macOS 15.4 (Darwin 25.3.0)
  • Launch command: claude --dangerously-skip-permissions --teammate-mode in-process
  • Project settings: "defaultMode": "bypassPermissions" in .claude/settings.local.json
  • User settings: "skipDangerousModePermissionPrompt": true in ~/.claude/settings.json

What I've Tried

  • Setting "defaultMode": "bypassPermissions" in project settings — still prompts
  • Adding "Edit", "Write", "Read" to the allow list — still prompts
  • Adding path-specific rules like "Edit(/path/to/project/**)" — still prompts
  • "skipDangerousModePermissionPrompt": true in user settings — still prompts

The only workaround is selecting "Yes, allow all edits during this session (shift+tab)" at the start of each session.

Notes

Bash tool calls are correctly bypassed — only Edit/Write prompt. This appears to be a regression or an intentional but undocumented carve-out for file modification tools.

View original on GitHub ↗

5 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/36192
  2. https://github.com/anthropics/claude-code/issues/37181
  3. https://github.com/anthropics/claude-code/issues/40852

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

b-davs · 5 months ago

Same issue on v2.1.91, macOS 15.7.4 (x86_64).

--dangerously-skip-permissions prompts for Edit and Write on every call — was working fine until ~April 1-2.

Potentially relevant: my local ~/.claude.json has a recently-rolled-out feature flag tengu_harbor_permissions: true (under cachedGrowthBookFeatures). The timing of this flag appearing lines up with when the regression started. No individual timestamps on feature flags to confirm exactly when it flipped, but it wasn't there before.

Settings for reference:

  • ~/.claude/settings.json has "skipDangerousModePermissionPrompt": true
  • No project-level permission overrides
  • tengu_disable_bypass_permissions_mode: false (not explicitly disabled)
AaronHallAttorney · 4 months ago

👍

ashwin-ant collaborator · 4 months ago

This was fixed in v2.1.98 — Subagents spawned in-process now inherit the parent's permission mode, so --dangerously-skip-permissions applies to their Edit/Write calls too. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.

github-actions[bot] · 4 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.