[BUG] "Accept Edits On" Mode on Windows 11 requires manual confirmation for edits (v1.0.103 regression)
Status Fixed / completed
Maintainer reply ✓ Yes — bogini
Activity 11 comments · opened Sep 4, 2025 · closed Sep 4, 2025
💡 Likely answer: A maintainer (bogini, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Claude CLI version: 1.0.103 (affected), 1.0.100 (working)
- Operating System: Windows 11
- Terminal: Command Prompt/PowerShell (installed via npm, not WSL)
Bug Description
File edit confirmation dialog appears even though I am on "accept edits on" mode in Claude Code CLI
version 1.0.103, while they work correctly in version 1.0.100.
Steps to Reproduce
- Install Claude Code CLI version 1.0.103 via npm on Windows 11
- Navigate to a project directory with code files
- Enable "accept edits on" mode
- Request Claude to make edits to existing files (e.g., adding comments,
modifying code)
- Observe that edits still require a confirmation dialog
Expected Behavior
When "accept edits on" mode is enabled, Claude should be able to
successfully apply edits to files without requiring manual approval for
each change.
Actual Behavior
Edits require permission confirmation using version 1.0.103, even with
"accept edits on" mode enabled.
Additional Context
- Downgrading to version 1.0.100 resolves the issue completely
- The problem appears to be a regression introduced in version 1.0.103
11 Comments
---
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
---
same error I just run /init in react next.js start-up prj and then ask me lots of permission in auto-accept mode, even read file also need permission
Same here, it doesn't work at all on my end.
The constant confirmation loop needed is driving me insane.
I wasn't able to fix this by wildcard allowing Read, Write, Edit or Update commands.
Same here, it happened to me since yesterday, and it is not only for edit, but it seems to extend to Read, Grep, Find, Search and other similar commands. The permissions are already whitelisted in settings.json and in the project itself (for its source folders).
Another thing I noticed is that in /claude/settings.local.json, it's adding duplicate "Read(<my directory>)" multiple times.
Thank you for the bug report. We've identified the root cause: a Windows path handling bug in our permission system that was causing "accept edits on" mode to fail on Windows platforms. This regression was introduced in v1.0.103.
The fix has been included as part of v1.0.105. Please update to the latest version to resolve this issue.
Sorry for the trouble!
The bug subsists in version 1.0.107 (Claude Code).
I can confirm, this bug still exists in in version 1.0.107 (Claude Code), the issue hasn't been fixed.
@rudolf-bardos @Sead-world Are you seeing Claude add rules in POSIX format? Like
"Read(//c/Users/alice/**)"@bogini The rules are being added in Windows format
"Read(C:\\Users\\rudolf\\Downloads/**)",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.