{"version":"2.1.208","anchor":"set-max-thinking-tokens-null-or-omitted-now-resets-to-sessio","canonical_anchor":"set-max-thinking-tokens-null-or-omitted-now-resets-to-sessio","heading":"set_max_thinking_tokens: null or omitted now resets to session default","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208\/e\/set-max-thinking-tokens-null-or-omitted-now-resets-to-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.208","markdown":"### set_max_thinking_tokens: null or omitted now resets to session default\n\n**What**\n\nWhen calling `set_max_thinking_tokens` with `max_thinking_tokens` omitted or null, thinking now resets to the session default rather than keeping the previously-set mid-session override. This makes it possible to undo a thinking budget adjustment without restarting the session.\n\n**Details**\n\n- Previously, `max_thinking_tokens: null` had ambiguous behavior\n- Now: omitting or setting to null clears any mid-session budget override back to the spawn-time budget\n- For sessions where thinking is disabled, this keeps thinking disabled\n- `max_thinking_tokens` must be an integer (or null); non-integer numbers are now rejected\n\n**Evidence**\n\nUpdated `set_max_thinking_tokens` description (search for `\"When max_thinking_tokens is omitted or null, thinking resets to the session default\"`)"}