{"version":"2.1.288","anchor":"content-hash-normalises-crlf-via-latin1-replaceall","canonical_anchor":"content-hash-normalises-crlf-via-latin1-replaceall","heading":"Windows line endings handled differently when Claude Code checks file contents","tier":"internal","area":"File Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/content-hash-normalises-crlf-via-latin1-replaceall","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Windows line endings handled differently when Claude Code checks file contents\n\nClaude Code now uses a different method to treat Windows line endings when it computes a file's fingerprint\n\n**Unclear.** It has not been confirmed that the new method always gives exactly the same fingerprint.\n\n**What**\n\nClaude Code computes a fingerprint of a file's contents, called a hash, so it can tell whether the file has changed. Before computing it, Claude Code turns Windows-style line endings into the plain kind. It now does this with a different method.\n\n**Why**\n\nThe fingerprints are expected to come out the same as before. Only the way they are computed has changed.\n\n- Area: File Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}