{"version":"2.1.271","anchor":"onsetmaxthinkingtokens-now-reuses-the-shared-thinking-config","canonical_anchor":"onsetmaxthinkingtokens-now-reuses-the-shared-thinking-config","heading":"onSetMaxThinkingTokens now reuses the shared thinking-config resolver","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/onsetmaxthinkingtokens-now-reuses-the-shared-thinking-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### onSetMaxThinkingTokens now reuses the shared thinking-config resolver\n\nSetting max thinking tokens now uses the same shared logic as other thinking-config settings\n\n**What**\n\nThe handler that sets the maximum number of \"thinking\" tokens (used for extended reasoning) in the SDK\/bridge REPL no longer computes its own on\/off state directly. It now calls the same shared helper used elsewhere, which can also resolve an \"adaptive\" thinking mode when no explicit value is given.\n\n**Why**\n\nThis is an internal consolidation so thinking-token settings are resolved the same way everywhere, reducing the chance of inconsistent behavior between different entry points.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}