{"version":"2.1.265","anchor":"remote-tool-call-protocol-adds-a-read-baseline-field","canonical_anchor":"remote-tool-call-protocol-adds-a-read-baseline-field","heading":"Remote tool-call protocol adds a read_baseline field","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remote-tool-call-protocol-adds-a-read-baseline-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote tool-call protocol adds a read_baseline field\n\nRemote tool-call requests can now include a read_baseline field\n\n**Unclear.** What read_baseline is used for or how it affects tool-call approval is not stated in the finding.\n\n**What**\n\nThe internal message format used for remote\/cloud tool-call requests (part of the remote-control protocol) now accepts a `readBaseline` value, which gets sent out as `read_baseline` in the request, but only when no approval has been given yet.\n\n**Why**\n\nThis is an internal protocol addition for how Claude Code communicates with remote or cloud-connected sessions; it does not change anything a user directly interacts with.\n\n- Area: Elsewhere\n- Names: `read_baseline`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}