{"version":"2.1.296","anchor":"file-write-detects-lossy-decoding","canonical_anchor":"file-write-detects-lossy-decoding","heading":"File writes now check whether a file could be read cleanly","tier":"internal","area":"File Editing","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/file-write-detects-lossy-decoding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### File writes now check whether a file could be read cleanly\n\nWhen Claude Code re-reads a file before writing to it, it now also notes whether the file's text could be read without loss\n\n**Unclear.** What Claude Code does when a file could not be read cleanly is not stated.\n\n**What**\n\nBefore writing to a file, Claude Code re-reads it. It now also notes whether the file's text could be read without losing anything, for example characters it could not make sense of.\n\n**Why**\n\nThis could help avoid damaging files that are not stored in the usual text format.\n\n- Area: File Editing\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}