{"version":"2.1.283","anchor":"sdk-apply-flag-settings-can-now-refuse-a-model-choice-and-sh","canonical_anchor":"sdk-apply-flag-settings-can-now-refuse-a-model-choice-and-sh","heading":"SDK model setting can now be refused with a restricted-model warning","tier":"notice","area":"Agents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/sdk-apply-flag-settings-can-now-refuse-a-model-choice-and-sh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### SDK model setting can now be refused with a restricted-model warning\n\nA model sent by an SDK host through `apply_flag_settings` can now be refused, with a warning naming the default model and the one in effect\n\n**Unclear.** What makes a model choice count as refused under the new check is not clear.\n\n**What**\n\nThe SDK lets other programs (called hosts) run Claude Code and control it. A host can send `apply_flag_settings` to change settings, including the model. Claude Code now has an extra check that can refuse the model sent this way. When it does, the model is not applied, and a restricted-model warning names the default model and the model actually in effect.\n\nBefore, the model was refused only when it was blocked and had no step-down model to fall back to.\n\n**Why**\n\nA host that changes the model this way may now see the change refused and replaced by a warning, rather than applied.\n\n- Area: Agents\n- Names: `apply_flag_settings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}