{"version":"2.1.241","anchor":"clearer-wording-for-clearing-the-thinking-display-override","canonical_anchor":"clearer-wording-for-clearing-the-thinking-display-override","heading":"Clearer wording for clearing the thinking display override","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.241\/e\/clearer-wording-for-clearing-the-thinking-display-override","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.241","markdown":"### Clearer wording for clearing the thinking display override\n\nA schema description was reworded to explain that clearing the thinking display setting restores Claude Code's own default.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Affects `max_thinking_tokens` and `thinking_display` on the extended-thinking control request.\n- No gate; visible to anyone reading the schema.\n\n**Evidence**\n\n`null clears that override so Claude Code's default display handling applies again`\n\n- Area: Elsewhere\n- Names: `--thinking-display`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}