{"version":"2.1.323","anchor":"bridge-control-response-errors-carry-error-code-unsupported","canonical_anchor":"bridge-control-response-errors-carry-error-code-unsupported","heading":"Remote Control error replies now mark unsupported requests with an error code","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-control-response-errors-carry-error-code-unsupported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote Control error replies now mark unsupported requests with an error code\n\nWhen a remote session gets a request it does not support, the error reply now carries `error_code: unsupported_request`\n\n**What**\n\nRemote Control lets you drive a Claude Code session from somewhere else, such as another device. When the session gets a request it does not support, it sends back an error reply. That reply now includes `error_code` set to `unsupported_request`. Before, the reply held only its type, the request ID and the error text.\n\n**Why**\n\nA remote client can now tell an unsupported request apart from other failures. Anyone who builds tools that read these replies should expect the extra field.\n\n- Area: Remote Control\n- Names: `unsupported_request`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}