{"version":"2.1.314","anchor":"set-model-control-request-no-longer-times-out-with-verdict-p","canonical_anchor":"set-model-control-request-no-longer-times-out-with-verdict-p","heading":"Model switch requests from host programs no longer time out while pending","tier":"notice","area":"Agents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/set-model-control-request-no-longer-times-out-with-verdict-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Model switch requests from host programs no longer time out while pending\n\nA set_model request now waits for the switch to finish with no deadline, and the 'still pending' error and later 'applied' notice are gone\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). A host can ask Claude Code to change model with `set_model`. Claude Code now waits for the result of that request with no time limit.\n\n- The `set_model` handler no longer has a deadline. Before, if the result was not ready in time, it replied with the error code `verdict_pending` and told the user the outcome later.\n\n- The \"This model switch is still pending\" error and the later \"The pending model switch was applied\" notices are removed.\n\n- The remote bridge, which connects Claude Code to sessions elsewhere, no longer passes a deadline (`deadlineMs`, taken from `setModelVerdictDeadlineMs`) when waiting on a `set_model` result.\n\n**Why**\n\nHosts now get one final answer once the model switch is settled, instead of an early error followed by a separate notice. A host that relied on a quick reply should expect the request to wait until the switch is decided.\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: yes"}