Startup model resolution now checks for a settings-provided model before falling back to ANTHROPIC_DEFAULT_MODEL. The resolution order is now CLI flag, then ANTHROPIC_MODEL env var, then the model from settings, then ANTHROPIC_DEFAULT_MODEL, giving a settings.json-configured default precedence over the legacy env-var default.
Names in the bundleANTHROPIC_DEFAULT_MODELANTHROPIC_MODEL
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Model configuration touched a line naming ANTHROPIC_MODEL after this was published.
Admins can also configure the organization default to override user selection. With override on, it takes precedence over the `model` value in user, project, and local settings, so a model you save with `/model` applies for the current ses…model-config see the edit
Confirmed since
Anthropic's documentation has since written up ANTHROPIC_DEFAULT_MODEL, on Roll out an LLM gateway for your organization.
| Default model and aliases | The model that new sessions start on by default, and the models that aliases such as `opus` and `sonnet` resolve to, are [built into each version](/docs/en/model-config#pin-models-for-third-party-deployments) …llm-gateway-rollout see the edit
Confirmed since
Anthropic's documentation has since written up ANTHROPIC_MODEL, on Plugins reference.
| `--model <model>` | Model for the agent under test | Each case's `model`, else `ANTHROPIC_MODEL` if set, else Claude Code's default |plugins-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up ANTHROPIC_MODEL, on Plugins reference.