Blanket Edit/Write permissions not auto-approved in dontAsk/acceptEdits mode (v2.1.80)

Resolved 💬 3 comments Opened Mar 20, 2026 by krishna-goje Closed Mar 20, 2026

Description

Blanket "Edit" and "Write" permissions in settings.json allow list are not being auto-approved. Claude Code prompts for permission on every file edit/write despite having these permissions configured.

This worked correctly until recently — regression in v2.1.80.

Settings (relevant excerpt)

{
  "permissions": {
    "allow": [
      "Write(//Users/krishnagoje/**)",
      "Edit(//Users/krishnagoje/**)",
      "Edit",
      "Write",
      "Read"
    ],
    "defaultMode": "dontAsk"
  }
}

Steps to Reproduce

  1. Add blanket "Edit" and "Write" to permissions.allow in ~/.claude/settings.json
  2. Set defaultMode: "dontAsk"
  3. Start a new session
  4. Ask Claude to create or edit any file (e.g., a markdown file in a project folder)
  5. Result: Permission prompt appears asking "Do you want to create X?"

Expected Behavior

With blanket "Edit" and "Write" in the allow list + dontAsk mode, ALL file edits and writes should auto-approve without prompting.

Actual Behavior

Every Edit/Write prompts for user approval, even on regular files (not settings.json or other protected files).

Screenshot attached shows the prompt appearing for a simple markdown file creation despite blanket Write permission.

Environment

  • Claude Code version: 2.1.80
  • OS: macOS (Darwin 25.1.0)
  • Mode tested: Both dontAsk and acceptEdits — neither auto-approves

Impact

This is a significant productivity regression. Users who configured blanket permissions to work autonomously now have to manually approve every single file operation, defeating the purpose of the permission system.

Additional Context

  • Path-scoped permissions (Write(//Users/krishnagoje/**)) also don't auto-approve
  • Both defaultMode: "dontAsk" and manual switch to acceptEdits exhibit the same behavior
  • This was working correctly in prior versions (approximately 1-2 weeks ago)

View original on GitHub ↗

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