What do Claude Code's model aliases such as opus, sonnet, fable, best and opusplan resolve to, and why is default not one of them?
answer
- names for a family, not a version
- the provider changes the answer
- Opus 5.5 since 2.1.280
- opusplan switches at the plan boundary
- pin with ANTHROPIC_DEFAULT_OPUS_MODEL
basics
~20 sAliases name a family that moves forward: at Claude Code 2.1.286 on the Anthropic API, opus is Opus 5.5 and sonnet is Sonnet 5.5, while other providers can lag. opusplan uses opus in plan mode and sonnet otherwise; default only clears an override.
solid answer
~50 sAn alias selects the recommended model of a family for your provider, and it changes as Claude Code releases. At 2.1.286 on the Anthropic API, `opus` is Opus 5.5 (since v2.1.280) and `sonnet` is Sonnet 5.5 (since v2.1.284); on Bedrock and Agent Platform `sonnet` is still Sonnet 4.5, and on Foundry `opus` is Opus 4.6. `haiku` selects the Haiku model for simple tasks, `fable` selects Fable 5.1, and `best` selects Fable where you have it and otherwise the same model as `opus`. `opusplan` runs `opus` while plan mode is on and `sonnet` for execution, and `opus[1m]` or `sonnet[1m]` request the 1M-token window where it is not native. `default` is not an alias: it clears the override and falls back to your account's default. To pin a version, use a full name such as `claude-opus-5-5` or set `ANTHROPIC_DEFAULT_OPUS_MODEL`.
code
bash · 6 lines# Plan on Opus, execute on Sonnet, for this session
claude --model opusplan
# Pin what the opus alias means before rolling out to a team
export ANTHROPIC_DEFAULT_OPUS_MODEL='claude-opus-5-5'
claude --model opusgo deeper
Recall the alias names and what each is for: opus for hard reasoning, sonnet for daily coding, haiku for simple tasks, and that default resets rather than selects.
Explain that aliases move with releases and differ by provider, how opusplan splits at plan mode, and how a full model name or ANTHROPIC_DEFAULT_OPUS_MODEL pins a version.
Show you would pin aliases before a third-party rollout, and recognize answers about older targets as release history rather than errors of concept.
Argue when a team should ride aliases and when a version change must be a gated decision, given that aliases update silently with Claude Code itself.
## Aliases name a family, not a version A **model alias** is a short name, such as `opus` or `sonnet`, that Claude Code resolves to a specific model when the session runs. The mapping depends on two things: the **Claude Code release** you run, because each release can move an alias to a newer model, and the **provider** you reach Claude through, because not every provider offers the newest model on the same day. A **full model name**, such as `claude-opus-5-5`, stays on that version; Claude Code warns you when a requested model is scheduled for retirement or remapped. That is the whole trade: an alias keeps you current without editing anything, a full name keeps you on exactly one version. ## What each alias selects at 2.1.286 on the Anthropic API | Alias | Selects | |---|---| | `opus` | the latest Opus: Opus 5.5 | | `sonnet` | the latest Sonnet: Sonnet 5.5 | | `haiku` | the fast, efficient Haiku model, for simple tasks | | `fable` | Fable 5.1 (Fable 5 in Claude apps gateway sessions) | | `best` | whatever `fable` resolves to where Fable is available to you, otherwise the same model as `opus` | | `opus[1m]`, `sonnet[1m]` | the alias with a 1M-token window; `sonnet[1m]` has no effect when `sonnet` is already Sonnet 5.5 or Sonnet 5, whose window is natively 1M | | `opusplan` | `opus` while plan mode is on, `sonnet` for execution | | `default` | not an alias: clears any override and returns to your account's default | On some plans Fable usage bills to usage credits rather than the plan's included limits, so `best` can carry a cost difference that `opus` does not. ## The provider changes the answer | Provider | `opus` | `sonnet` | |---|---|---| | Anthropic API | Opus 5.5 | Sonnet 5.5 | | Claude Platform on AWS | Opus 5.5 | Sonnet 4.6 | | Amazon Bedrock, Google Cloud's Agent Platform | Opus 5.5 | Sonnet 4.5 | | Microsoft Foundry | Opus 4.6 | Sonnet 4.5 | Where an alias lands on an older model, you reach the newer one by naming it in full or by setting `ANTHROPIC_DEFAULT_OPUS_MODEL` or `ANTHROPIC_DEFAULT_SONNET_MODEL`. On Bedrock, Agent Platform, Foundry and Claude Platform on AWS the docs tell administrators to pin versions with those variables before a rollout, because the built-in default can lag and may not be enabled in every account. ## Version history that explains stale answers - **v2.1.284**: `sonnet` moved to Sonnet 5.5 on the Anthropic API. - **v2.1.280**: `opus` moved to Opus 5.5 on the Anthropic API, Claude Platform on AWS, Bedrock and Agent Platform. - **v2.1.257**: `fable` moved to Fable 5.1, except in Claude apps gateway sessions. - **v2.1.219**: `opus` moved to Opus 5. A candidate who says `opus` means an Opus 4 model is describing an earlier release, not a wrong concept. ## How `opusplan` behaves `opusplan` is a fixed split at the **plan-mode boundary**: 1. While plan mode is active, requests go to whatever `opus` resolves to (or `ANTHROPIC_DEFAULT_OPUS_MODEL` if set). 2. Once you leave plan mode and Claude executes, requests go to whatever `sonnet` resolves to (or `ANTHROPIC_DEFAULT_SONNET_MODEL`). Each phase uses its own model's context window. Where those windows are not natively 1M, `opusplan[1m]` asks for 1M in both phases. `opusplan` does not judge task difficulty; for a model that consults a stronger one mid-task, Claude Code has a separate advisor feature. Plan mode itself is a separate topic. ## `default`, and pinning for a team `default` resolves by account type: Opus 5.5 on Pro, Max, Team, Enterprise and the Anthropic API, and on Claude Platform on AWS, Bedrock and Agent Platform; Sonnet 4.5 on Foundry. An organization default model, when an admin sets one, replaces that. Fable is never the account default on any plan. Practical rules for a team lead: - Use aliases on the Anthropic API when you want everyone to move with Claude Code releases. - Use a full name such as `claude-opus-5-5`, or an `ANTHROPIC_DEFAULT_*_MODEL` variable, when a version change must be a deliberate decision. - On third-party providers, pin before rollout and upgrade by changing the variable and redeploying. ## Checking what an alias became - The **session header** and **`/status`** name the model actually in use, which is the quickest way to settle what `opus` means on a given machine today. - When the requested model has a scheduled retirement date or is automatically remapped to a newer version, Claude Code shows a **warning naming the requested model**: a startup notice in interactive sessions, and a line on stderr in `claude -p` runs with the default text output. - On a third-party provider, setting an `ANTHROPIC_DEFAULT_*_MODEL` variable replaces that family's built-in rows in the `/model` picker with one row for the pinned model, so the picker itself shows what the alias is pinned to. If two developers disagree about what an alias does, compare the Claude Code version, the provider and any `ANTHROPIC_DEFAULT_*_MODEL` variables before anything else; those three explain almost every difference.
- Why might the same opus alias give a colleague on Bedrock a different session than you get on the Anthropic API?Alias targets are per provider, and on some providers the default lags the newest release or is not enabled in every account. On Bedrock and Agent Platform an unavailable default produces a notice and a fall back to an earlier version; Foundry shows errors instead. Pinning `ANTHROPIC_DEFAULT_OPUS_MODEL` and `ANTHROPIC_DEFAULT_SONNET_MODEL` to explicit IDs makes every user resolve the alias the same way.
- What does the best alias select, and why might it cost more than opus?`best` selects whatever `fable` resolves to when Fable is available to you, and otherwise the same model as `opus`. Depending on plan and seat tier, Fable usage can bill to usage credits instead of the plan's included limits, and an interactive session normally asks for consent before such a request (Enterprise members on organization billing see no prompt).
- Does opusplan[1m] change anything on the Anthropic API today?Rarely. Each opusplan phase uses the context window of the alias it runs, and on the Anthropic API the current Opus and Sonnet already run with a native 1M window, so both phases get it. `opusplan[1m]` matters where those windows are not 1M natively; selecting it with `/model` needs v2.1.265 or later.
- opus means the same Opus version on every provider
- default is just another alias that selects Sonnet
- opusplan routes each request by how hard the task looks
- An alias stays pinned to the version present at install time
- On the Anthropic API you need sonnet[1m] for 1M on Sonnet 5.5
Assumes Claude Code 2.1.286: opus resolves to Opus 5.5 from v2.1.280 and sonnet to Sonnet 5.5 from v2.1.284 on the Anthropic API.