Deleting a session from a transcript has a new backend routine with retries, disabled here.
A precondition-guarded session-delete rewrite runs only on the tengu_hover_rest path, which is off.
tengu_hover_rest Off in both readingsThe 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: on
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's wrong with this entry?
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.
- 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.
Tombstone removal abandoned on the paged path
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
CLAUDE_CODE_HOVER_RESTgives a local override for the new credential and settings storageBoth mention hover rest
-
v2.1.238
The v5 storage choice reads the environment variable first
Both mention hover rest
-
v2.1.238
Plaintext credential store gained an in-process cache
Both mention hover rest