The tengu_api_query and tengu_api_success telemetry events now carry a thinkingPrefixMismatchBehavior field. It's populated from block_binding.mismatch_behavior, which is attached to the thinking config only when a specific beta header is present and the request doesn't already carry its own thinking key.
New thinkingPrefixMismatchBehavior field on API telemetry, tied to a 'block_binding' beta feature
API telemetry can now log a thinking-block mismatch setting, but only under a specific unreleased beta header.
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
TelemetryArea: what it touches
In DevelopmentKind: in v2.1.263,
What probably matters to youSection of the release