{"version":"2.1.323","anchor":"remote-control-set-model-request-callback-and-structured-un","canonical_anchor":"remote-control-set-model-request-callback-and-structured-un","heading":"Remote sessions can ask to change the model, and get clearer errors for unsupported requests","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-control-set-model-request-callback-and-structured-un","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions can ask to change the model, and get clearer errors for unsupported requests\n\nRemote sessions now pass on requests to change the model and answer unsupported requests with a structured error code\n\n**What**\n\nWhen a session is driven from somewhere else, the remote side sends control requests, which are instructions about how the session should behave. Two of these have changed:\n\n- A request to set the model is now recognised and passed on for Claude Code to act on.\n\n- A request type Claude Code does not support now comes back as a structured error with the code `unsupported_request`. Before, it was a plain error message.\n\n**Why**\n\nRemote clients can ask for a different model during a session. Tools connecting remotely can also tell an unsupported request apart from other failures by reading a code instead of parsing a message.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}