{"version":"2.1.288","anchor":"model-validation-marks-server-refused-models","canonical_anchor":"model-validation-marks-server-refused-models","heading":"Model checks now record when the server refuses a model","tier":"internal","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/model-validation-marks-server-refused-models","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Model checks now record when the server refuses a model\n\nWhen the API says a model is not found or not available for your account, the model check now marks it as refused by the server\n\n**Unclear.** It is not clear what Claude Code does differently once a model is marked as refused.\n\n**What**\n\nWhen Claude Code checks whether a model can be used, the result now records separately that the server refused the model. This happens when the API says the model was not found or is not available for your account. A rate-limit reply saying credits are required also counts, except in some specific known cases.\n\nBefore, the result only recorded not found, permission denied or credits required.\n\n**Why**\n\nOther parts of Claude Code can now tell a firm refusal from the server apart from a temporary failure.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}