{"version":"2.1.307","anchor":"set-model-control-response-now-reports-the-model","canonical_anchor":"set-model-control-response-now-reports-the-model","heading":"Model switch requests from host programs now report which model is in use","tier":"notice","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/set-model-control-response-now-reports-the-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Model switch requests from host programs now report which model is in use\n\nThe reply to a host's request to change model now names the model the next turn will use, even when the change is refused\n\n**What**\n\nA host is a program that runs Claude Code, for example through the SDK (the kit for building your own programs on top of Claude Code). When a host asks Claude Code to switch model with `set_model`, the reply now includes the model that the session's next turn will run as. This is included even when the switch was refused.\n\n**Why**\n\nHosts can show the model that is really in use after a switch fails, instead of assuming the switch worked.\n\n- Area: Agents\n- Names: `set_model`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}