Key takeaways
- The model configuration docs say Opus 5.5 requires Claude Code v2.1.280 or newer, so run claude update first.
- On Microsoft Foundry the opus alias still resolves to Opus 4.6, so select claude-opus-5-5 by its full name.
- An availableModels allowlist, an organization restriction or a model setting in a settings file can also hide or override it.
Opus 5.5 not showing in Claude Code is almost always one of five things: your Claude Code is older than v2.1.280, your provider maps the opus alias to a different model, an availableModels allowlist hides it, your organization disabled it, or a model setting in a settings file overrides your choice. The fix is usually claude update, then /model claude-opus-5-5. This guide follows the Claude Code model configuration docs and the setup docs, as read on November 9, 2026.
Step 1: update Claude Code to v2.1.280 or newer
According to the model configuration docs, Opus 5.5 requires Claude Code v2.1.280 or later. Check your version, then update:
claude --version
claude update
When an update installs, claude update reports Successfully updated from <old version> to version <new version>. If you are already current, it says Claude Code is up to date (<version>). Restart Claude Code after updating, because updates take effect the next time you start it.
How you installed Claude Code changes what you run:
| Install method | How to update |
|---|---|
| Native installer | Updates itself in the background, or run claude update |
| Homebrew | brew upgrade claude-code or brew upgrade claude-code@latest, depending on the cask |
| WinGet | winget upgrade Anthropic.ClaudeCode |
| npm | npm install -g @anthropic-ai/claude-code@latest |
The docs say Homebrew, WinGet and Linux package manager installs do not auto-update by default. They also warn against npm update -g, which may not move you to the newest release.
If you are on the stable channel
The setup docs describe two release channels. latest is the default and gets new versions as soon as they ship. stable is typically about a week old. The docs add that a newly launched model can need a Claude Code version newer than the stable channel serves, and the fix is to move to the latest channel. Set it in /config under Auto-update channel, or in settings.json:
{
"autoUpdatesChannel": "latest"
}
Homebrew users pick the channel by cask: claude-code is stable, claude-code@latest is latest. If claude update says you are current but your version is still below 2.1.280, run claude doctor to see the result of the last update attempt.
Step 2: select Opus 5.5 with /model
Inside a session, type /model with no argument to open the picker, or name the model directly:
/model opus
/model claude-opus-5-5
To start a session on it:
claude --model claude-opus-5-5
In the picker, Enter switches and saves the choice as your default for new sessions. Pressing s switches for this session only. Typing /model <name> behaves like Enter.
Step 3: check which model the opus alias means on your provider
The opus alias tracks the recommended Opus for your provider. According to the docs, as of November 9, 2026:
| Provider | opus resolves to |
sonnet resolves to |
haiku resolves to |
|---|---|---|---|
| Anthropic API | Opus 5.5 | Sonnet 5.5 | Haiku 5.5 |
| Claude Platform on AWS | Opus 5.5 | Sonnet 4.6 | Haiku 4.5 |
| Amazon Bedrock, Google Cloud's Agent Platform | Opus 5.5 | Sonnet 4.5 | Haiku 4.5 |
| Microsoft Foundry | Opus 4.6 | Sonnet 4.5 | Haiku 4.5 |
On Microsoft Foundry, opus points to Opus 4.6, so select Opus 5.5 by its full name instead. The same goes for any third-party deployment where you want a specific version. You can also pin what the alias resolves to:
export ANTHROPIC_DEFAULT_OPUS_MODEL=<your-opus-model-id>
The default option also depends on your account. Per the docs it resolves to Opus 5.5 on Pro, Max, Ultra, Team, Enterprise, the Anthropic API, Claude Platform on AWS, Amazon Bedrock and Google Cloud's Agent Platform, and to Sonnet 4.5 on Microsoft Foundry. An organization default set by an Enterprise admin can replace it.
Step 4: look for an allowlist or a denylist
Administrators can limit the picker with availableModels in managed settings. A list that does not permit Opus 5.5 hides it:
{
"availableModels": ["sonnet", "haiku"]
}
Entries can be a family such as sonnet, a version prefix, or a full model ID. The docs also describe deniedModels, which blocks specific releases (v2.1.283 or later) and is read from managed settings only:
{
"availableModels": ["opus", "sonnet"],
"deniedModels": ["claude-opus-5-5"]
}
On Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry, a model ID you list appears in the picker only if it starts with anthropic., or if you add it to a modelPicker lineup. If you do not manage the settings yourself, ask your admin. Enterprise admins can also disable individual models in the claude.ai admin console. The docs say those restrictions reach Anthropic API and LLM gateway sessions only. On other providers, availableModels is the control.
Step 5: find a model setting that overrides your choice
A model value in project or managed settings overrides what you pick with /model at every launch. The model priority order in the docs, highest first, is:
/model <alias|name>during a sessionclaude --model <alias|name>at startup- The
ANTHROPIC_MODELenvironment variable - The
modelfield in a settings file ANTHROPIC_DEFAULT_MODELfor new sessions (v2.1.236 or later)
The docs say the startup header names the file responsible when a settings value is pinning the model. Remove or change the model field there. Resumed sessions with --resume, --continue or /resume normally keep the model they were saved with, so start a fresh session to see the change.
Common problems
- Mistyped model name. If a bad value is set through
--model,ANTHROPIC_MODELormodel, the error shows up on the first request, not at startup. Check the spelling ofclaude-opus-5-5. - A request fails on an older version. The model configuration docs point to the "Claude Code does not support this model" error entry. Updating to v2.1.280 or later is the first fix.
- Opus 5.5 is there but efforts differ. Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable default to
mediumeffort, according to the docs. Use/effortto change it. - Requests switch to another model. The docs say Opus 5.5 and Fable route safety-flagged requests to other models. Biology-flagged requests re-run on Opus 5, and cybersecurity-flagged requests on Opus 4.8. Setting
switchModelsOnFlagtofalsemakes Claude Code ask first. - Older models seem to vanish. The 2.1.319 release notes (November 6, 2026) say the
/modelpicker now groups older models under a "More models" row.
If none of this helps, run /doctor inside Claude Code for an automated check of your installation and settings, or claude doctor from your shell if claude will not start.
Where to go next
For the update commands in more detail, see our guide on how to update Claude Code. To switch models while keeping a session going, the model configuration page covers opusplan, fallback chains and the 1M-token context option.
Frequently asked questions
Which Claude Code version do I need for Opus 5.5?
The model configuration docs say Opus 5.5 requires Claude Code v2.1.280 or later. Run claude --version to check and claude update to upgrade.
How do I switch to Opus 5.5 in Claude Code?
Type /model claude-opus-5-5 in a session, or start with claude --model claude-opus-5-5. The /model command with no argument opens the picker.
Why does claude update say I am up to date but I still lack Opus 5.5?
You may be on the stable channel, which the docs say can lag behind a newly launched model. Set autoUpdatesChannel to latest in /config or settings.json.
Why is Opus 4.6 selected on Microsoft Foundry?
The docs list Opus 4.6 as what the opus alias resolves to on Microsoft Foundry. Select claude-opus-5-5 by its full name or set ANTHROPIC_DEFAULT_OPUS_MODEL.
Sources
- Model configurationAnthropic
- Advanced setupAnthropic
- Claude Code changelogAnthropic
- TroubleshootingAnthropic

