{"version":"2.1.236","anchor":"a-special-thinking-block-check-is-wired-up-but-always-answer","canonical_anchor":"a-special-thinking-block-check-is-wired-up-but-always-answer","heading":"A special thinking-block check is wired up but always answers no","tier":"soon","area":"Thinking","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/a-special-thinking-block-check-is-wired-up-but-always-answer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### A special thinking-block check is wired up but always answers no\n\nHandling for a special kind of thinking block exists, but the check always answers no here.\n\n**What**\n\nNew 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.\n\n**Details**\n\n- The matcher variable starts as `null` and nothing in the build assigns it, so the check always returns false and none of those branches run.\n\n**Evidence**\n\n`redacted_thinking`\n\n- Area: Thinking\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}