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.285 ·

set_max_thinking_tokens now checks thinking_display and can refuse part of a request

The SDK set_max_thinking_tokens request now validates thinking_display, refuses bad parts, and does not apply the value "highlights"

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

Unclear Which combinations of the two values cause a refusal is not known.

What

The SDK (the kit for driving Claude Code from your own program) can send a set_max_thinking_tokens request to change the thinking budget (max_thinking_tokens) and how thinking is shown (thinking_display). The request is now checked as a whole:

  • Validation: max_thinking_tokens and thinking_display are checked together. If the check fails, the reply is set_max_thinking_tokens: part of the request refused.
  • "highlights": asking for thinking_display "highlights" produces a message that it "was not applied", and the display stays as it was. The accepted values are "summarized" and "omitted".

Why

If your program changes thinking settings, part of a request can now be rejected. Check the reply rather than assuming the new display setting took effect, and use "summarized" or "omitted".

Read from
Names in the bundleset_max_thinking_tokensmax_thinking_tokensthinking_display
What the documentation says
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 doubtWhich combinations of the two values cause a refusal is not known.

See this entry in the whole of v2.1.285 →

Feedback