The new storage layer now touches nearly every part of the product but is never actually created.
Storage-handle mentions grew from 37 to 689, yet the only factory returns nothing and its gate 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.227: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
An optional storage handle now threads through session and transcript loading, MCP reconnect, plugin loading, daemon and background jobs, team files, scheduled tasks, memory directories and agent sidecars: mentions grow from 37 in v2.1.226 to 689 here. Every call site branches on whether the handle exists and otherwise takes the existing filesystem path. The only factory that would create one returns nothing regardless of its tengu_hover_rest gate, which itself falls back to off, so behaviour is unchanged everywhere.
- Call sites choose between a "v5" arm and the existing "raw" arm.
- There is a diagnostic for the case where two callers disagree about which backend a shared plugin load uses: "joining a plugin load that an earlier caller started without the storage backend (tengu_hover_rest); this caller's backend is not used for it".
- This release ships the plumbing only.
dt(nui, { tryCreateV5Backend: () => dSf, pinStorageV5: () => RBe });, joining a plugin load that an earlier caller started without the storage backend (tengu_hover_rest); this caller's backend is not used for it
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.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
-
v2.1.223
Deep-link registration and cleanup sentinels can be stored as state keys
Both mention storage backend