{"version":"2.1.265","anchor":"remote-tool-calls-now-attach-a-read-baseline-snapshot-befo","canonical_anchor":"remote-tool-calls-now-attach-a-read-baseline-snapshot-befo","heading":"Remote tool calls now send a read baseline for host-side verification","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remote-tool-calls-now-attach-a-read-baseline-snapshot-befo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote tool calls now send a read baseline for host-side verification\n\nRemote tool calls now attach a read baseline snapshot so the remote host can verify a file hasn't changed before an edit runs\n\n**Unclear.** The finding describes the mechanism but not confirmed downstream behavior, such as what the host does if a file changed.\n\n**What**\n\nWhen Claude Code sends the first, unapproved request for a remote tool call to a host, it now includes a `readBaseline` field built from the session's record of files it has read. A new `noteReadBaselineSent` callback fires once the host confirms it received this baseline (`read_baseline`), and the tool-call dispatch logic now tracks a `readBaselineSent` flag on the call's outcome, tying into a `project_sync` read-baseline lookup.\n\n**Why**\n\nThis lets a remote host check, before executing an edit-style tool call, that the file it's about to modify hasn't changed since Claude last read it there, reducing the risk of an edit overwriting changes it never saw.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}