Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Claude Code explains when managed settings block a model

A new message says when a model was skipped for a check, fallback or upgrade because managed settings do not allow it

You'll notice Improvements
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ModelsArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release
What

Managed settings are settings an administrator installs centrally. Claude Code now has a message saying a model was skipped for a check, a fallback or an upgrade because managed settings do not allow it as spelled. The reasons it gives:

Why

Administrators and users get an explanation when a managed model policy blocks a model, instead of the model silently not being used.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhere this message is shown is not stated.
Anthropic's release notes agreeFixed Bedrock and Vertex startup model checks ignoring an enforced availableModels list, which could collapse /model to one Opus row

See this entry in the whole of v2.1.287 →

Feedback