Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

New 'tether' subsystem re-creates a thinking thread when the server drops thinking on a prefix mismatch

A new tether subsystem recreates a thinking thread when the server drops earlier thinking due to a prefix mismatch

Nothing to try yet In Development
JSON All of v2.1.280
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Session ThreadingArea: what it touches
In DevelopmentKind: in v2.1.280,
In DevelopmentSection of the release
What

Claude 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.

Why

This 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.

Read from
Feature flag
tengu_wondrous_acorn Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.280: 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.

Read once, for one account on one subscription tier, against v2.1.280. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns {"enabled":true,"min_continues":3} for tengu_wondrous_acorn, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"enabled":false} for tengu_wondrous_acorn, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns {"enabled":true,"min_continues":3} for tengu_wondrous_acorn, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_wondrous_acorn

See this entry in the whole of v2.1.280 →

Feedback