[Bug] Persistent Read Permissions Prompt and Auto-Edit Functionality Failure
Status Fixed / completed
Maintainer reply ✓ Yes — bogini
Workaround ✓ Mentioned in thread ↓
Activity 6 comments · opened Sep 4, 2025 · closed Sep 4, 2025
💡 Likely answer: A maintainer (bogini, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
the auto edit isnt working well. also read used to work, why do i have to keep accepting Claude Code read permissions, even when i say to allow in the seesion it keeps asking me.
Environment Info
- Platform: win32
- Terminal: mintty
- Version: 1.0.103
- Feedback ID: 063b16bc-8abb-4a8d-a26f-91b21a890d12
Errors
[{"error":"Error: Request was aborted.\n at yP.makeRequest (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:979:3864)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at runNextTicks (node:internal/process/task_queues:69:3)\n at listOnTimeout (node:internal/timers:555:9)\n at process.processTimers (node:internal/timers:529:7)","timestamp":"2025-09-04T08:53:46.040Z"},{"error":"Error: Request was aborted.\n at I31._createMessage (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:970:7955)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at runNextTicks (node:internal/process/task_queues:69:3)\n at listOnTimeout (node:internal/timers:555:9)\n at process.processTimers (node:internal/timers:529:7)","timestamp":"2025-09-04T08:58:26.544Z"},{"error":"AbortError: The operation was aborted\n at abortChildProcess (node:child_process:716:27)\n at AbortSignal.onAbortListener (node:child_process:786:7)\n at [nodejs.internal.kHybridDispatch] (node:internal/event_target:827:20)\n at AbortSignal.dispatchEvent (node:internal/event_target:762:26)\n at runAbort (node:internal/abort_controller:447:10)\n at abortSignal (node:internal/abort_controller:433:3)\n at AbortController.abort (node:internal/abort_controller:466:5)\n at Timeout._onTimeout (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:749:75)\n at listOnTimeout (node:internal/timers:594:17)\n at process.processTimers (node:internal/timers:529:7)","timestamp":"2025-09-04T09:00:36.003Z"},{"error":"Error: EPERM: operation not permitted, rename 'C:\\Users\\HP EliteBook\\Documents\\Projects\\cake_mom-web_app\\index.html.tmp.25776.1756980195632' -> 'C:\\Users\\HP EliteBook\\Documents\\Projects\\cake_mom-web_app\\index.html'\n at Module.renameSync (node:fs:1021:11)\n at Object.renameSync (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:677:7337)\n at _N (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:753:646)\n at sy (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:749:4)\n at Object.call (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1873:853)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async uO5 (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3555:11273)\n at async DdB (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3555:7472)\n at async hO5 (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3555:6335)\n at async bO5 (file:///C:/Users/HP%20EliteBook/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3555:5872)","timestamp":"2025-09-04T10:03:15.647Z"}]
6 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Having the same issue, seems like the maintainers are sleeping ...
Temporary Fix for Windows Users 🛠️
This workaround successfully reverts the version and resolves the issue.
Here's a step-by-step guide:
/config.Tabkey./exitto close the console.``
npm install -g @anthropic-ai/claude-code@1.0.102
I'm experiencing the same issue. During a single session working on files in a directory, I had to approve read/edit permissions approximately 7 times for the same directory path. Each time I approved it, the next file operation would ask for permission again instead of remembering my previous approval.
Platform: Windows
Claude Code Version: 1.0.103 (Claude Code)
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!
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.