A write is refused if the file changed since the preview you approved.
What's wrong with this entry?
When a write is applied with a recorded content hash, Claude Code now re-hashes the file on disk first and refuses the write if the contents no longer match, so an edit you approved cannot silently clobber a change made in the meantime.
- The internal write path takes a baseHash argument; the check runs whenever a caller supplies one.
- On mismatch it throws instead of writing, reporting that the file changed since the edit was previewed.
file changed since the edit was previewed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
PDF reads return the document and page images
Both mention file tool
-
v2.1.246
Read separates the file it opens from the file it reports
Both mention file tool
-
v2.1.246
Write results say when content was replaced without showing a diff
Both mention file tool