Under the hood
Setting max thinking tokens now uses the same shared logic as other thinking-config settings
What
The 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.
Why
This is an internal consolidation so thinking-token settings are resolved the same way everywhere, reducing the chance of inconsistent behavior between different entry points.