Claude Code "does not support this model; version … is required"
Claude Code's 400 claude_code_version_too_old: which binary made the request, why claude update on stable falls short, and the fix for the app, SDK, Pi and Hermes.
Anthropic’s API refuses a model to a Claude Code older than the version that model needs. The message names both numbers: the first is the version that made the request, the second the minimum. Update the binary that made the request, then start a new session. For a Claude Code you installed, that is claude update. If you are on the stable channel, the update can stop short of the minimum, because a newly launched model can need a version stable does not serve yet: switch to the latest channel, update again, and check with claude --version. If the first number in the message is not the version claude --version prints, the request came from something else: the desktop app, the VS Code extension, an Agent SDK app, or a tool such as Pi or Hermes signing in with your Claude account. Update that one instead.
API Error: 400 Claude Code 2.1.219 does not support this model; version 2.1.255 or newer is required. Run 'claude update', or update the Claude desktop app, then try again.CopiedWhat the message means
Per Anthropic’s error reference, this 400 means “your Claude Code version is below a required minimum”, and “the server checks per model”. The response carries the error code claude_code_version_too_old. The key line for working out what to update: “The version the API checks is the one reported by the Claude Code binary that made the request.”
There is no single number to remember. Each model has its own minimum, and new models raise it. Reports on GitHub show the pattern: Fable 5.1 asked for 2.1.251 in September 2026, Opus 5.5 for 2.1.280 later that month, and Fable 5.2 for 2.1.290 in November. Read the minimum from your own message.
A second wording means your organization sets the floor, not the model:
API Error: 400 Claude Code 2.1.240 is older than the minimum version required by your organization's policy. Run 'claude update', or update the Claude desktop app, to continue.CopiedThat one has no way round it in the session. Update before you continue.
Update Claude Code, and leave the stable channel if you need to
Run the update, then look at what you have:
claude update
claude --versionCopiedIf the version is still below the minimum, check your release channel. Claude Code has two. latest is the default and gets every release as it ships. stable is “typically about one week old”. Anthropic’s setup page says it directly: “A newly launched model can require a Claude Code version newer than the stable channel serves. To run the model now, move to the latest channel.” The GitHub reports for Fable 5.1 and Opus 5.5 both started from a stable install, and a commenter on the first put it as “Fable 5.1 was made only available on the latest channel.”
For the installer’s copy (the claude at ~/.local/bin/claude), change the channel in /config under Auto-update channel, or in ~/.claude/settings.json:
{
"autoUpdatesChannel": "latest"
}CopiedThen run claude update again. If you had also pinned a minimumVersion to move to stable without a downgrade, switching back to latest in /config clears it. Rerunning the installer with a channel sets the default too: “The channel you choose at install time becomes your default for auto-updates.”
curl -fsSL https://claude.ai/install.sh | bash -s latestCopiedOther installs choose their channel elsewhere and do not take the setting:
- Homebrew: the
claude-codecask is stable, andclaude-code@latestis latest. - apt, dnf or apk: the repository you registered is the channel. On Debian or Ubuntu, point the
debline at the latest repository, then upgrade:
echo "deb [signed-by=/etc/apt/keyrings/claude-code.asc] https://downloads.claude.ai/claude-code/apt/latest latest main" \
| sudo tee /etc/apt/sources.list.d/claude-code.list
sudo apt update && sudo apt upgrade claude-codeCopied- npm:
npm install -g @anthropic-ai/claude-code@latest. Anthropic says to avoidnpm update -g, which “may not move you to the newest release.”
If your organization pins the channel or version through managed settings, the docs’ answer is to ask your admin to change it. Claude Code on Linux covers the channels, the installer and holding a version on a server.
When the number in the message is not your claude
Compare the first version in the error with claude --version. If they differ, the request came from another binary or tool, and updating your claude will not change it.
- The Claude desktop app runs its own copy of Claude Code. Update the app. In one report, the app’s copy was on 2.1.260 while the user’s own
~/.local/bin/claudewas on 2.1.280 and ran Opus 5.5 fine. In the app, the model appeared greyed out with “Update Claude to use this model on this computer”. - The VS Code extension bundles a binary. Update the extension.
- An app built on the Agent SDK runs the binary its SDK package bundles. Upgrade the SDK package and restart the app, or rebuild it if it is compiled to a single executable.
- Pi signed in with a Claude account reports a Claude Code version of its own. With Fable 5.2, Pi sent 2.1.280 against a minimum of 2.1.290. A maintainer answered “fixed on main” on November 10, 2026, and Pi 1.5.2’s notes list “Fixed Anthropic OAuth requests reporting an outdated Claude Code version”. Update Pi.
- Hermes with Anthropic sign-in: an open issue reports the message with Claude Code 2.1.0 as the version that made the request, against a minimum of 2.1.280. It found that two side paths, the usage lookup and the auxiliary client, send a fixed old version, while the main chat sends the detected one. As of November 19, 2026, no fix is linked. Watch the issue and update Hermes when one lands.
How these tools use a Claude plan, and what Anthropic’s terms say about it, is in your Claude subscription in Hermes, Pi or OpenCode.
Updated, and the old version still runs
If claude update reports success and the error comes back with the old number, there is likely a second Claude Code on the machine. Anthropic’s docs name two causes: a second installation, or a leftover shell alias from an older installer. An npm global copy left beside the installer’s ~/.local/bin/claude is one such pair. List every claude the shell can see, and the version of the one it runs:
type -a claude
claude --versionCopiedKeep one and remove the others with their own uninstall (npm uninstall -g @anthropic-ai/claude-code for npm). A shell that already ran claude can keep its remembered path. One user on the Fable 5.1 issue fixed it with hash -r and a new login shell after updating.
A job started by cron or a systemd timer uses its own PATH, so it can run a different claude from your login shell. Use the full path in the job. Running Claude Code headless on a schedule sets that up. A session that is already running keeps its version until it ends, so start a new one after the update.
Keep working while you update
For the per-model wording, the docs’ stopgap is to switch to a model your version supports: /model in the CLI, setModel() on the TypeScript SDK’s Query object in streaming input mode, or set_model() on the Python SDK’s ClaudeSDKClient. A script that pins the new model with --model fails on every run until the binary it calls is updated.