Error: File has been unexpectedly modified. Read it again before attempting to write it
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Nov 25, 2025 · closed Feb 27, 2026
I'm having the issue 'Error: File has been unexpectedly modified. Read it again before attempting to write it' persistently after updating to version 2.0.52, making it impossible to use the tool properly.
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.0.52
- Feedback ID: f8492b10-1fa5-414d-80b9-9e7db08ee6c8
Errors
[{"error":"Error: File has been unexpectedly modified. Read it again before attempting to write it.\n at Object.call (file:///C:/Users/luizr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:2106:754)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async Gh5 (file:///C:/Users/luizr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:2219:20784)","timestamp":"2025-11-25T01:43:39.119Z"}]
11 Comments
I have exactly the same issue:
Interesting observation. The problem seems not to be in CLI itself, just tried to downgrade to CLI v2.0.53 (this was working yesterday) and then 2.0.52 and 2.0.51 - nothing helps.
Claude's bug report:
@claude fix it
Reporting the SAME issue...nothing new to add regarding details but the bugs that are cropping up in Claude Code are making me regret renewing my Max subscription. I left for the downgraded output and performance, only to come back to the same. Lesson is now LEARNED.
It got fixed ages ago. I guess in a few days after. Seems to be a misconfiguration because of some other package updates. But if you got it only now you may try to downgrade CLI till it get work. There are many clones of this report and in some of them were exact versions that worked perfectly.
My current version of CLI (2.0.61) is working well.
I hear you but this volleying between versions approach reintroduces old
bugs that I was glad to see fixed and therefore leaves me to choose how
much I wish to be inconvenienced as opposed to the issue(s) actually being
fixed with a forward momentum vs accepting regressive workarounds.
On Tue, Dec 9, 2025 at 4:01 AM Dimonka2 @.***> wrote:
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
@claude fix it
i had this issue many times today and yesterday
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.