{"version":"2.1.319","anchor":"internal-write-tracking-now-stores-a-content-hash","canonical_anchor":"internal-write-tracking-now-stores-a-content-hash","heading":"Claude Code now records a fingerprint of the files it writes itself","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/internal-write-tracking-now-stores-a-content-hash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Claude Code now records a fingerprint of the files it writes itself\n\nWhen Claude Code marks a file as written by itself, it now keeps a fingerprint of the content as well as the time\n\n**What**\n\nClaude Code keeps a note of files it has just written itself. That note now holds the time of the write and a content hash (a short code worked out from the file's contents). The check that reads the note now hands back that hash, rather than only a yes or no based on how recently the write happened.\n\n**Why**\n\nComparing content, not just timing, can make Claude Code better at telling its own edits apart from changes made outside it.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}