{"version":"2.1.280","anchor":"new-tether-subsystem-re-creates-a-thinking-thread-when-the","canonical_anchor":"new-tether-subsystem-re-creates-a-thinking-thread-when-the","heading":"New 'tether' subsystem re-creates a thinking thread when the server drops thinking on a prefix mismatch","tier":"soon","area":"Session Threading","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-tether-subsystem-re-creates-a-thinking-thread-when-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'tether' subsystem re-creates a thinking thread when the server drops thinking on a prefix mismatch\n\nA new tether subsystem recreates a thinking thread when the server drops earlier thinking due to a prefix mismatch\n\n**What**\n\nClaude Code adds a large new set of internal functions that track, per conversation thread, whether \"thinking\" content (Claude's visible reasoning) was newly created versus carried over from earlier in the conversation. When the server reports a `prefix_mismatch` that invalidates thinking content Claude Code had already sent, this new logic either recreates the thread on its next request, or, if the drop happened very early after a thread was just recreated, falls back to sending the rest of the conversation without a `thread` id at all.\n\n**Why**\n\nThis is meant to keep a conversation working smoothly when the server can no longer accept previously sent thinking content, by automatically recovering instead of leaving the conversation in a broken state.\n\n- Flag `tengu_wondrous_acorn`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Session Threading\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}