{"version":"2.1.290","anchor":"set-model-can-now-accept-an-unconfirmed-model-and-returns-u","canonical_anchor":"set-model-can-now-accept-an-unconfirmed-model-and-returns-u","heading":"Model switches can go through without server confirmation","tier":"use","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/set-model-can-now-accept-an-unconfirmed-model-and-returns-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Model switches can go through without server confirmation\n\nA `set_model` request now applies the model even if the server could not confirm it, and the reply says `unconfirmed: true`\n\n**Unclear.** What leaves the server unable to confirm a model is not clear.\n\n**What**\n\nPrograms that drive Claude Code through the SDK (the software development kit for building on top of it) can ask it to switch models with `set_model`. If the server cannot confirm the requested model, Claude Code now applies it anyway and adds `unconfirmed: true` to its reply. Before, a failed server check rejected the switch.\n\nThe list of error codes also gains `workspace_diff_pending`, used by `get_workspace_diff`.\n\n**Why**\n\nA program using the SDK can now tell when a model switch went through without the server confirming it, rather than having the switch rejected.\n\n- Area: SDK\n- Names: `set_model`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}