{"version":"2.1.265","anchor":"file-writeedit-stale-read-checks-now-carry-remote-call-read","canonical_anchor":"editwrite-tools-can-now-detect-that-a-file-changed-on-a-di","heading":"Edit and Write tools detect remote file changes by host","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/file-writeedit-stale-read-checks-now-carry-remote-call-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Edit and Write tools detect remote file changes by host\n\nEdit\/Write now catch files changed on a different machine since Claude last read them remotely, and say which machine\n\n**What**\n\nWhen a file was read through a remote call (for example during a remote session), the Write and Edit tools now record a `readBaseline` \u2014 a size-and-hash snapshot of the file taken at read time \u2014 along with `servedOn`, the hostname the file was actually read from.\n\nBefore writing, the tools re-read a bounded portion of the file and compare it against that baseline. If it no longer matches, Claude Code now throws a specific error naming the host: \"File has been modified on {host} since this session read it. Read it again there...\" instead of the old generic staleness message.\n\n**Why**\n\nThis prevents Claude from overwriting changes that happened on a different machine than the one it's currently checking, and tells you exactly where to go re-read the file instead of leaving you with a vague warning.\n\n- Area: Elsewhere\n- Names: `readBaseline`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}