{"version":"2.1.265","anchor":"file-modified-since-read-errors-now-name-the-host-when-multi","canonical_anchor":"file-modified-since-read-errors-now-name-the-host-when-multi","heading":"File-modified-since-read errors now name the host when multi-host sessions are involved","tier":"notice","area":"Multi-Host Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/file-modified-since-read-errors-now-name-the-host-when-multi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### File-modified-since-read errors now name the host when multi-host sessions are involved\n\nThe 'file changed since you read it' error now names which host to re-read the file on, in multi-host sessions\n\n**What**\n\nWhen Claude Code detects that a file was modified after it was last read, and the session spans multiple hosts (machines), the error message now tells the model exactly which host to re-read the file on, using an explicit `_host` parameter in the `Read` tool call. Previously the message was generic and didn't specify a host.\n\n**Why**\n\nIn multi-host sessions, a file with the same path can exist independently on different machines. Naming the host removes ambiguity about where the file actually changed, so the model re-reads the correct copy before retrying the write.\n\n- Area: Multi-Host Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}