{"version":"2.1.283","anchor":"edit-treats-a-file-refreshed-from-disk-behind-the-models-ba","canonical_anchor":"edit-treats-a-file-refreshed-from-disk-behind-the-models-ba","heading":"Edit refuses to change a file whose new contents Claude never saw","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/edit-treats-a-file-refreshed-from-disk-behind-the-models-ba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Edit refuses to change a file whose new contents Claude never saw\n\nIf Claude Code quietly refreshed its copy of a file after it changed on disk, Edit now treats Claude's read as out of date\n\n**Unclear.** Not every situation that quietly refreshes a file's record is known.\n\n**What**\n\nClaude Code remembers which files Claude has read so it can tell when a file changed afterwards. Sometimes that memory is refreshed after a file changes on disk, without Claude being shown the new contents. Edit now treats a read like that as out of date, whatever the file's last-modified time says. The edit fails with the stale-read error unless it still applies to the file as it is now.\n\nBefore, a read only counted as out of date when the file had been modified after it was read and its contents differed.\n\n**Why**\n\nThis stops Claude from editing a file based on a version of it that it never actually looked at.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}