SDK sessions can set a thinking token limit and thinking display when they start.
What's wrong with this entry?
When a session starts, the control channel now sends a set_max_thinking_tokens request carrying a maximum thinking token count, a thinking display setting, or both, if the caller supplied them.
- Sent only when
thinking.maxThinkingTokensorthinking.displayis provided; otherwise nothing extra goes out. - Sits next to the existing set-mode request, which switched from generating a random UUID to a shared id helper.
subtype: "set_max_thinking_tokens"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent