{"version":"2.1.273","anchor":"file-read-integrity-now-also-validated-by-content-digest","canonical_anchor":"file-read-integrity-now-also-validated-by-content-digest","heading":"File read integrity now also validated by content digest","tier":"notice","area":"File Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/file-read-integrity-now-also-validated-by-content-digest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### File read integrity now also validated by content digest\n\nClaude Code now also checks a content digest, not just byte offset, to detect if a file changed before editing\n\n**What**\n\nWhen 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.\n\n**Why**\n\nThe 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.\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}