{"version":"2.1.317","anchor":"remote-tools-unsupported-protocol-check-before-approving-se","canonical_anchor":"remote-tools-unsupported-protocol-check-before-approving-se","heading":"Remotely served tool calls can now be refused as an unsupported protocol","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-tools-unsupported-protocol-check-before-approving-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remotely served tool calls can now be refused as an unsupported protocol\n\nBefore approving a tool call served remotely, Claude Code now checks the session's interface and refuses with unsupported_protocol if it does not fit\n\n**Unclear.** What makes a session's interface fit or not fit is not stated.\n\n**What**\n\nWhen Claude Code serves a tool call, an action Claude takes such as running a command, to a remote session, it now checks whether the session's interface fits first. If it does not, the call is refused with the code `unsupported_protocol` before any pending approval request is replaced or any allow is used.\n\n**Why**\n\nIt changes how approvals work for tools used through a remote session: some calls are now turned down early instead of going through approval.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}