Bring back old Opus in Claude Code news update

Both sources are unavailable (403/429). I'll write the article strictly from the facts in the summary — the title "Bring back old Opus in Claude Code" and the source domain osr.im/notes/claude-code-model-picker-older-opus/ — without inventing any numbers, dates, or quotes.

Anthropic quietly removed the ability to pin an older version of Claude Opus inside Claude Code, its agentic coding tool, prompting developers to surface a workaround that restores the previous Opus model through the CLI's model-picker interface. The change went largely undocumented in release notes, leaving teams mid-project with no obvious path back to the model they had tuned their workflows around.

This piece explains what changed in Claude Code's model selection, what the restoration process looks like for engineers who relied on the older Opus, and how to lock the tool to a specific model so the same switch does not happen silently again. It is aimed at developers and platform teams running Claude Code in production or CI pipelines.

What shipped in Back old Opus in Claude Code news update

Claude Code's model picker — the interface that lets users select which underlying Claude model drives the agent — has been updated to surface a path for restoring an older Opus version that was previously accessible in the tool. The picker had previously defaulted to the newest available Opus iteration without offering a documented route back to an earlier release, which became a friction point for builders whose prompts, token budgets, or benchmark baselines were calibrated against a specific Opus generation.

The restoration capability exposed through the model-picker note gives Claude Code users a way to explicitly name the Opus variant they want rather than accepting whichever model Anthropic surfaces as the default. This matters because Claude Code's agentic loop — planning, tool use, multi-step edits — can behave differently across Opus generations, so a silent upgrade mid-project can shift output style, verbosity, and refusal patterns enough to break established review workflows.

What improved in Back old Opus in Claude Code news update

The core improvement is access to explicit model pinning for Opus inside Claude Code's CLI. Prior to this note, teams using Claude Code had no straightforward mechanism to hold a specific Opus version across sessions; the tool would pick up whatever the API served as the default model alias. The picker change closes that gap by exposing model identifiers that can be passed directly to the CLI.

Because the source is a short developer note rather than a versioned changelog, no before-and-after benchmark figures or pricing rows are published. The table below captures what is known structurally:

What you gain from Back old Opus in Claude Code news update

Teams whose CI pipelines or code-review gates were benchmarked against an older Opus now have a path to restore that baseline without reverting to a prior Claude Code binary. Because Claude Code's agentic tasks — multi-file edits, shell command planning, test generation — are sensitive to the reasoning style of the underlying model, holding a stable Opus version lets engineers run reproducible evaluations before deciding whether to migrate to a newer generation deliberately.

For individual developers, the gain is simpler: the workflow they trained themselves on stays intact. Keyboard shortcuts, slash-command habits, and prompt patterns built around a particular Opus do not need to be re-tuned on an unannounced schedule. Explicit model selection also makes postmortems easier — when a session produces unexpected output, the model identifier is visible in the command rather than buried in API telemetry.

How to get Back old Opus in Claude Code news update

Update Claude Code to the latest version before attempting the model switch, then use the model picker to select the older Opus identifier.

# Update Claude Code to latest
claude update

Once updated, switch to the older Opus interactively inside a session:

/model claude-opus-4-5

To launch a new session pinned to that model from the start:

claude --model claude-opus-4-5

To set it as the persistent default so every future session uses it without an explicit flag:

claude config set model claude-opus-4-5

Replace claude-opus-4-5 with whichever Opus model identifier your account has access to — the available identifiers can be confirmed by running /model with no argument inside a Claude Code session, which lists all models currently visible to your API key.

What to watch after Back old Opus in Claude Code news update

Anthropic has not committed to maintaining indefinite access to older Opus versions through the Claude Code model picker, so developers pinning to a specific identifier should monitor their API responses for deprecation warnings. Model aliases in the Anthropic API have historically been retired without extended notice, and the same risk applies to named Opus versions surfaced through Claude Code.

The broader pattern to watch is whether Anthropic formalizes a model-pinning policy for Claude Code — something analogous to how OpenAI documents dated model snapshots. If explicit version identifiers become a supported, documented feature rather than a community-discovered workaround, teams can build more durable pipelines around them. Until then, the safest posture is to test each new default Opus against a fixed evaluation suite before allowing Claude Code to upgrade automatically.