Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

'highlights' thinking display: unavailability now depends on the model, not only the provider

The 'highlights' thinking display now only errors on Bedrock, Vertex or a gateway for models released before Claude Opus 4.7, and its reasons are reworded

Group of 2 You'll notice No documentation found Improvements
JSON All of v2.1.310
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HighlightsArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release

Unclear Only the option's description changed, so it is not shown whether newer models on those providers actually stop getting the error.

What

'highlights' is a setting for how Claude's thinking is shown, offered as a beta (early-access) feature. Claude Code now treats its availability on other API providers, the services Claude Code talks to, differently:

  • When it errors: the description of the thinking_display setting now says 'highlights' gives an error on Amazon Bedrock, Google Vertex AI or a Claude apps gateway only for models released before Claude Opus 4.7. Before, it gave an error on any such provider that gets no first-party-only betas, whatever the model.
  • The reason shown: the separate reason "Claude Code does not send first-party-only beta features to this session's API provider" was removed. It was folded into the model reason, which changed from "this session's model does not support it" to "this session's model does not support it on this API provider".

Why

People using a third-party provider with a newer model may now be able to use 'highlights', and anyone who cannot will see a different explanation.

Read from
Names in the bundlethinking_display
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 doubtOnly the option's description changed, so it is not shown whether newer models on those providers actually stop getting the error.

See this entry in the whole of v2.1.310 →

Feedback