Handling for a special kind of thinking block exists, but the check always answers no here.
Detection of a "special" thinking block needs a registered matcher that this build does not have, so the branches never run.
What's wrong with this entry?
New helpers ask whether an assistant message begins with a "special" thinking block, requiring both a thinking string and a signature string plus a registered matcher. Where the answer is yes, the message stops counting as thinking-only for context assembly, the streaming thinking panel is cleared rather than updated, and the message is treated as a real assistant turn.
- The matcher variable starts as
nulland nothing in the build assigns it, so the check always returns false and none of those branches run.
redacted_thinking
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.227
Resuming an interrupted thinking block accepts more model spellings
Both mention thinking
-
v2.1.224
Effort picker can show relative cost, gated off
Both mention thinking
-
v2.1.224
Effort slider can show what each level costs
Both mention thinking