Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

Deleting a session from a transcript has a storage-backend implementation

Deleting a session from a transcript has a new backend routine with retries, disabled here.

Nothing to try yet No documentation found In Development
JSON All of v2.1.234
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Storage BackendArea: what it touches
In DevelopmentKind: in v2.1.234,
In DevelopmentSection of the release

A precondition-guarded session-delete rewrite runs only on the tengu_hover_rest path, which is off.

What

A new routine removes a session's records from a transcript by reading the tail and rewriting it under a precondition that fails if another writer got there first, retrying up to three times. It runs only on the storage backend path gated by tengu_hover_rest, which is off in this build.

Details
  • Files whose records are not in the tail take a paged slow path, and there is a file-size ceiling above which the removal is abandoned rather than attempted.
Evidence

Tombstone removal abandoned on the paged path

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundletengu_hover_rest
Feature flag
tengu_hover_rest Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.234: off

Read once, for one account on one subscription tier, against v2.1.234. 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 off for tengu_hover_rest, 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 nothing at all, having stopped carrying it for tengu_hover_rest, 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 →

See this entry in the whole of v2.1.234 →

Feedback