{"version":"2.1.268","anchor":"teleport-revert-now-marks-pending-thinking-block-stripping","canonical_anchor":"teleport-revert-now-marks-pending-thinking-block-stripping","heading":"Teleport revert now marks pending thinking-block stripping","tier":"internal","area":"Teleport","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/teleport-revert-now-marks-pending-thinking-block-stripping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Teleport revert now marks pending thinking-block stripping\n\nReverting a teleport session now flags pending thinking-block cleanup and skips one telemetry event\n\n**Unclear.** The finding does not explain what a teleport\/relay session is used for or what consuming the `relayThinkingStripOwed` flag does later.\n\n**What**\n\nWhen a teleport (relay) session reverts from active back to a non-active status, it now sets a `relayThinkingStripOwed` flag to true. It also now skips sending the \"upgrade teleport cache\" telemetry event specifically when the revert reason is `direct_served`.\n\n**Why**\n\nThis marks that thinking content (the model's intermediate reasoning) still needs to be stripped after a relay session reverts, and avoids emitting a telemetry event that wouldn't apply in the `direct_served` case.\n\n- Area: Teleport\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}