{"version":"2.1.315","anchor":"model-validation-errors-now-sanitise-the-model-name","canonical_anchor":"model-validation-errors-now-sanitise-the-model-name","heading":"Model error messages clean up the model name and add the server's explanation","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/model-validation-errors-now-sanitise-the-model-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Model error messages clean up the model name and add the server's explanation\n\nErrors about an unknown or unavailable model now clean up the model name you typed, and some add the server's own explanation\n\n**What**\n\nWhen you ask for a model that Claude Code cannot use, the error message repeats the model name you gave it. That name is now cleaned up before it is shown, rather than inserted exactly as typed. This applies to messages such as `Model '...' not found` and `is not available`, and to the details shown when Claude Code cannot check a model at all.\n\nTwo messages also now add a description sent by the server:\n\n- the one saying a model is not currently available for your account\n\n- the one saying a model is restricted by your organization's settings\n\n**Why**\n\nA mistyped or unusual model name can no longer put stray control characters, such as invisible codes that change how a terminal displays text, into an error message. The added description gives more context on why a model is unavailable.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}