A schema description was reworded to explain that clearing the thinking display setting restores Claude Code's own default.
What's wrong with this entry?
The control-protocol schema that lets an SDK client set extended thinking now explains the null case differently: passing null for thinking_display clears the override so Claude Code's own default display handling applies, rather than reverting to the API default. Wording only; the fields, the "summarized" and "omitted" values, and --thinking-display all behave as before.
- Affects
max_thinking_tokensandthinking_displayon the extended-thinking control request. - No gate; visible to anyone reading the schema.
null clears that override so Claude Code's default display handling applies again
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.240
Narration thinking is kept out of the live thinking preview
Both mention thinking display
-
v2.1.240
CLAUDE_CODE_THINKING_DISPLAY_UPDATES environment variable
Both mention thinking display
-
v2.1.240
Thinking display modes gated behind a server-side model capability
Both mention thinking display