Allow rules for Edit/Write don't auto-approve — still prompts user

Resolved 💬 3 comments Opened Feb 21, 2026 by yuxi-liu-wired Closed Feb 21, 2026

Description

Setting Edit and Write allow rules in .claude/settings.json does not auto-approve file edits. The user is still prompted for every edit, even when the path matches the allow rule.

Steps to reproduce

  1. Create .claude/settings.json in a project directory with:
{
  "permissions": {
    "allow": [
      "Edit(/home/user/project/**)",
      "Write(/home/user/project/**)",
      "Read(/home/user/project/**)"
    ]
  }
}
  1. Start a Claude Code session in that project directory
  2. Ask Claude to edit a file within the project (e.g. todo.md)
  3. Claude is prompted for permission despite the allow rule matching

Expected behavior

File edits matching an allow rule should be auto-approved without prompting.

Actual behavior

The user is prompted for every edit. The only workaround found was adding "defaultMode": "acceptEdits" to the settings, which raises the question: what is the purpose of the allow rules if they don't actually allow anything on their own?

Environment

  • Claude Code CLI
  • Linux (Kubuntu 24.04)

View original on GitHub ↗

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