{"version":"2.1.293","anchor":"read-baseline-retention-can-be-forced-per-file-state-cache","canonical_anchor":"read-baseline-retention-can-be-forced-per-file-state-cache","heading":"Claude Code can be told to always keep its record of what a file looked like when read","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/read-baseline-retention-can-be-forced-per-file-state-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Claude Code can be told to always keep its record of what a file looked like when read\n\nA store of file contents Claude Code has read can now be set to always keep its reference copy, whatever the general rule says\n\n**What**\n\nClaude Code remembers what a file looked like when it read it, so it can tell later whether the file has changed since. Whether it keeps that reference copy used to depend only on one general rule. A store of read files can now be set up to always keep it.\n\n**Why**\n\nThis affects how Claude Code notices that a file was changed after it was read.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}