A full in-memory storage backend ships, off unless you set an environment variable.
CLAUDE_CODE_HOVER_REST or tengu_hover_rest gate it; the flag falls back to 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.248: on
Read once, for one account on one subscription tier, against v2.1.248. 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 complete in-memory version of the new v5 storage backend now ships as its own chunk: a tree of directory, value and stream nodes with appends, tombstones, record replacement, leases, change subscriptions, scope listing and deletion, and per-log-channel byte budgets. Whether any of it is used depends on the CLAUDE_CODE_HOVER_REST environment variable, or otherwise the tengu_hover_rest flag, whose compiled fallback is off.
- Versions are strings shaped
s<epoch>.<generation>.<seq>. - Construction is wrapped in a guard that reports success or a
fell_backoutcome and, on failure, drops back to the legacy storage path.
v5 in-memory storage backend construction failed; this worker keeps no storage backend
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.234
Precomputed session resolution on resume, gated off
Both mention hover rest
-
v2.1.234
Resume reads the pre-compaction sidecar ahead of time
Both mention hover rest
-
v2.1.238
CLAUDE_CODE_HOVER_RESTgives a local override for the new credential and settings storageBoth mention hover rest