Your global config can be watched through the storage backend instead of the file, falling back if it fails.
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?
Claude Code watches ~/.claude.json so changes made by another running process are picked up. A new path subscribes to that config through the storage backend instead and stops watching the file once the subscription succeeds; if it fails, the existing file watcher stays in place.
- The config state now also records which backend supplies freshness and holds a one-shot claim for resubscribing.
- Requires both the storage v5 pin (
tengu_hover_rest, falling back to false) and a constructed backend, and this build cannot construct one, so the file watcher is what actually runs.
Watching ~/.claude.json for other processes through the storage interface
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.227
Settings can be pre-loaded through the v5 storage backend
Both mention json storage backend
-
v2.1.223
Compare-and-swap retry helper for versioned storage keys
Both mention storage backend
-
v2.1.223
Daemon lock and auto-update lock gained storage-backend implementations
Both mention storage backend