You'll notice
Claude Code now also checks a content digest, not just byte offset, to detect if a file changed before editing
What
When Claude Code verifies that a file hasn't changed since it was last read (before applying an edit), it now also compares a content digest (a fingerprint computed from the file's contents) against a stored digest. If the digests don't match, it reports the file as changed, in addition to the existing check based on byte offset.
Why
The byte-offset check alone could miss some cases where a file's contents changed without the size or offset appearing to shift. Checking a content digest as well makes it more reliable to catch edits made outside Claude Code before they get silently overwritten.