[BUG] Permission to read and edit files for session not being respected
Environment
- Platform (select one):
- [x] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.103 (Claude Code)
- Operating System: Windows 11
- Terminal: VSCode integration
Bug Description
Before today's update, I was able to give permission to Claude to read and make updates for the entire session, however, it doesn't appear like this is being respected anymore.
A possible prerequisite:
I restored a previous session's conversation and started from there.
Steps to Reproduce
- Give a set of actions to claude to fix, I gave 3 instructions: 2 small fixes and a feature request.
- Wait for Claude to ask for permission to read or edit files in a folder, when it does, give permission for this session (Option 2).
Expected Behavior
Claude continues to work on my files without asking for permission again (read or edit) during this session.
Actual Behavior
Claude asks for every single read and edit for files, as if I was choosing the 1st option (Yes) instead of the 2nd option (Yes, and accept all for this session)
Additional Context
I'm working on a web app, in python, that is fairly straightforward. These edits are on both static and code files for that project. It was working fine before the update this afternoon.
Note
As a workaround I'm launching claude with the --dangerously-skip-permissions option. This works, however, I'm closely watching the console to ensure it hasn't gone off the rails. So far it is OK, but this isn't a great workaround.
9 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is a new bug in 1.0.103 on Windows.
Noticed this too, and it's a big time waster. If I wanted to be nagged for every little thing I do, I would just use Codex haha.
Update - Yeah, this is painful, I'm going back to Roo until this is resolved.
Please resolve this issue swiftly. It's compromising many people's productivity.
This issue is pretty maddening!
Seriously, its difficult to work in large changes with this issue cropping up every few secs. Pls resolve urgently.
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!
Thank you @bogini and team for the quick turnaround - fix verified locally.
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.