An environment variable now takes priority over the server flag when picking the new storage backend.
CLAUDE_CODE_HOVER_REST is checked before the server flag for v5 storage, whose compiled fallback is false.
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.238: on
Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The code selecting the v5 storage backend checks CLAUDE_CODE_HOVER_REST before falling back to the tengu_hover_rest flag, whose compiled fallback is false.
- The variable is propagated to spawned sessions, so a pinned choice is inherited.
let e = V.CLAUDE_CODE_HOVER_REST ?? it("tengu_hover_rest", !1);
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.242
On-disk storage layer gains symlink and permission rules per data type
Both mention hover rest