Unclear Which models have a published-document target is not stated.
What
Claude Code picks a default model for each model family alias (sonnet, opus and haiku). These defaults used to be fixed in each build. Now:
- The default for a family can come from a document. Such a default is marked
fromDocument, and it can carry adocumentTargetnaming a model ID this build does not know. - The
ANTHROPIC_DEFAULT_*_MODELenvironment variables, such asANTHROPIC_DEFAULT_SONNET_MODEL, keep priority over these defaults. - In two places that check
modelOverrides(the setting that maps model IDs to your provider's IDs), entries that have adocumentTargetare no longer suppressed by amodelOverridesentry. One place returns the tier, environment variable and value for model tiers set by environment variables; the other checks the environment variables of each model entry. - A new check lists candidate models that fail an availability check.
- On Bedrock and Vertex, startup now also runs
checkBedrockDocumentDefaultsorcheckVertexDocumentDefaultsin the time left. When a document-configured default is not available on the account, a startup notice says "Default model: ... not available on this account - not used as this session's default". - New helpers decide whether a model name configured for a third-party provider (Bedrock, Vertex or Mantle) is usable. They check per-provider and everywhere default pins, and fall back to an older model in the same family when
modelOverridescovers the newer one.
Why
In practice, which model an alias such as sonnet points to is no longer decided only by the installed build. On Bedrock and Vertex you are told when such a default is not available to your account instead of it being used anyway.
Names in the bundlemodelOverrides
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which models have a published-document target is not stated.