{"version":"2.1.275","anchor":"new-telemetry-event-for-dropped-thinking-blocks","canonical_anchor":"new-telemetry-event-for-dropped-thinking-blocks","heading":"New telemetry event for dropped thinking blocks","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-telemetry-event-for-dropped-thinking-blocks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New telemetry event for dropped thinking blocks\n\nNew telemetry event tengu_thinking_drop logs when thinking blocks get stripped from a request\n\n**What**\n\nClaude Code now sends a telemetry event called `tengu_thinking_drop` whenever \"thinking\" blocks (the model's intermediate reasoning content) are removed from a request before it's sent, for example when there's a mismatch between the prefix of prior turns and the model currently bound to the session. The event records how many blocks and turns were affected, why they were dropped, which message positions were involved, and details of the client-side change that triggered the request.\n\n**Why**\n\nThis gives visibility into a case where reasoning content silently gets stripped out, which should help diagnose situations where thinking output unexpectedly disappears from a conversation.\n\n- Area: Telemetry\n- Names: `tengu_thinking_drop`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}