[BUG]
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Starting with version 2.1.121, every file-edit tool call (Edit / Write / NotebookEdit) shows a permission prompt, even though:
The corresponding tools are explicitly listed in permissions.allow ("Edit", "Write", "NotebookEdit")
The session is switched to Accept Edits or Auto mode via Shift+Tab
The prompt that appears is the standard one:
Do you want to make this edit to <filename>?
❯ 1. Yes
- Yes, allow all edits during this session (shift+tab)
- No
Downgrading to 2.1.120 with the identical settings.json restores expected behavior, so this is a regression introduced in 2.1.121.
Environment: macOS 26.4.1(25E253)
What Should Happen?
With "Edit", "Write", and "NotebookEdit" listed in permissions.allow, file-edit operations should proceed without a confirmation prompt (the behavior up through 2.1.120).
Additionally, switching to Accept Edits or Auto mode via Shift+Tab should suppress permission prompts for edit-class tools regardless of the static allow list.
Error Messages/Logs
Steps to Reproduce
- Install Claude Code 2.1.121 (latest channel).
- In ~/.claude/settings.json, set:
{
"permissions": {
"allow": ["Edit", "Write", "NotebookEdit"],
"defaultMode": "default"
}
}
- Launch Claude Code in any directory and have the assistant edit a file.
→ Observed: the permission prompt appears every time.
- Press Shift+Tab to switch to Accept Edits (or Auto) mode, then trigger another edit.
→ Observed: the prompt still appears.
- Exit and run the previous binary directly
With the same settings.json, repeat steps 3–4.
→ Observed: no prompts appear (expected behavior).
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.121
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗