{"version":"2.1.263","anchor":"new-thinkingprefixmismatchbehavior-field-on-api-telemetry-t","canonical_anchor":"new-thinkingprefixmismatchbehavior-field-on-api-telemetry-t","heading":"New thinkingPrefixMismatchBehavior field on API telemetry, tied to a 'block_binding' beta feature","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.263\/e\/new-thinkingprefixmismatchbehavior-field-on-api-telemetry-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.263","markdown":"### New thinkingPrefixMismatchBehavior field on API telemetry, tied to a 'block_binding' beta feature\n\nAPI telemetry can now log a thinking-block mismatch setting, but only under a specific unreleased beta header.\n\nThe `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.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}