Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.309 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

Vertex and Bedrock default models can come from a published model document

On Vertex and Bedrock, default models can now come from a published document per tier, falling back to models mapped in modelOverrides

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

When you use Claude Code through Google Vertex or Amazon Bedrock, it checks which default model it can use for each model tier. Before, the fallbacks came only from a list built into Claude Code. Now:

  • Each tier can take its target model from a published model document.
  • A model that is too old is treated as unavailable when it was a document default.
  • A model your administrator has mapped through modelOverrides counts as an accepted fallback.
  • Claude Code can check document defaults again and record any that turned out not to work.

On Vertex, this check is skipped when CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST is set.

Why

Vertex and Bedrock users may see different default models once published documents drive the choice.

See this entry in the whole of v2.1.310 →

Feedback