You can pin the new credential and settings storage backend yourself with one environment variable.
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 new v5 storage backend for credentials and settings can now be pinned with the CLAUDE_CODE_HOVER_REST environment variable, which takes precedence over the tengu_hover_rest server flag. That flag's built-in fallback is false, so the v5 backend stays off unless the server enables it or you set the variable.
- The decision is now latched once per process instead of re-read at each call site; the code warns if a later pin disagrees with the first.
- The variable was added to the list of
CLAUDE_CODE_*names forwarded to spawned sessions alongsideCLAUDE_CODE_REMOTE_SESSION_ID, so a pin carries into child sessions.
CLAUDE_CODE_HOVER_REST
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