{"version":"2.1.295","anchor":"remote-tool-protocol-version-negotiation","canonical_anchor":"remote-tool-protocol-version-negotiation","heading":"Remote tool runs now agree on a protocol version","tier":"internal","area":"Remote Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/remote-tool-protocol-version-negotiation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Remote tool runs now agree on a protocol version\n\nClaude Code and a remote worker now compare protocol versions and use the lower one, or report which side is too old\n\n**What**\n\nWhen tools run on a remote worker (another machine doing the work for Claude Code), the two sides now agree on a protocol version, which is a version number for how they talk to each other. The result is one of three:\n\n- The other side is too old.\n\n- This side is too old.\n\n- They agree, and both use the lower of the two versions.\n\nApproval of a tool request can now also carry a verdict supplied from the server. That verdict is removed before the request is forwarded on.\n\n**Why**\n\nA client and a worker on different versions can now tell when they cannot work together, instead of mismatching quietly.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}