Last read and last modification past millisecond #4268

Closed
opened 2026-02-16 17:43:14 -05:00 by yindo · 7 comments
Owner

Originally created by @klonuo on GitHub (Jan 5, 2026).

Originally assigned to: @rekram1-node on GitHub.

← Edit frontend/package.json 
Error: File /frontend/package.json has been modified since it was last read.
Last modification: 2026-01-05T23:29:26.516Z
Last read: 2026-01-05T23:29:26.194Z
Please read the file again before modifying it.

This happens quite too often, and it seems that last read is somehow milliseconds past last modified, while the model made the modification obviously.

Originally created by @klonuo on GitHub (Jan 5, 2026). Originally assigned to: @rekram1-node on GitHub. ``` ← Edit frontend/package.json Error: File /frontend/package.json has been modified since it was last read. Last modification: 2026-01-05T23:29:26.516Z Last read: 2026-01-05T23:29:26.194Z Please read the file again before modifying it. ``` This happens quite too often, and it seems that last read is somehow milliseconds past last modified, while the model made the modification obviously.
yindo closed this issue 2026-02-16 17:43:14 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 5, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #5840: [Tracking] Edit tool reliability: "modified since last read" errors (Undo/Redo & Persistence) - This is a tracking issue that covers the exact error you're experiencing with the Edit tool rejecting operations due to file modification timestamp conflicts.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 5, 2026): This issue might be a duplicate of existing issues. Please check: - #5840: [Tracking] Edit tool reliability: "modified since last read" errors (Undo/Redo & Persistence) - This is a tracking issue that covers the exact error you're experiencing with the Edit tool rejecting operations due to file modification timestamp conflicts. Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Jan 6, 2026):

@klonuo are u on wsl or windows?

@rekram1-node commented on GitHub (Jan 6, 2026): @klonuo are u on wsl or windows?
Author
Owner

@klonuo commented on GitHub (Jan 6, 2026):

Yes, WSL :)

@klonuo commented on GitHub (Jan 6, 2026): Yes, WSL :)
Author
Owner

@kfuglsang commented on GitHub (Jan 7, 2026):

Im getting this quite a lot on Windows as well - but without WSL.

@kfuglsang commented on GitHub (Jan 7, 2026): Im getting this quite a lot on Windows as well - but without WSL.
Author
Owner

@acidnik commented on GitHub (Jan 13, 2026):

i'm getting this on linux

@acidnik commented on GitHub (Jan 13, 2026): i'm getting this on linux
Author
Owner

@lord-carlos commented on GitHub (Feb 13, 2026):

I'm getting this on windows without WSL as well. Only opencode has the file open, no other tool.

@lord-carlos commented on GitHub (Feb 13, 2026): I'm getting this on windows without WSL as well. Only opencode has the file open, no other tool.
Author
Owner

@klonuo commented on GitHub (Feb 13, 2026):

@lord-carlos you can use OPENCODE_DISABLE_FILETIME_CHECK env var, more info: https://github.com/anomalyco/opencode/pull/6581

@klonuo commented on GitHub (Feb 13, 2026): @lord-carlos you can use OPENCODE_DISABLE_FILETIME_CHECK env var, more info: https://github.com/anomalyco/opencode/pull/6581
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4268