Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.227 ·

A new storage backend is wired through nearly everything, but never built

The new storage layer now touches nearly every part of the product but is never actually created.

Nothing to try yet In Development
JSON All of v2.1.227
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Storage BackendArea: what it touches
In DevelopmentKind: in v2.1.227,
What probably matters to youSection of the release

Storage-handle mentions grew from 37 to 689, yet the only factory returns nothing and its gate is off.

What

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.

Details
  • 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.
Evidence

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.

Read from
Feature flag
tengu_hover_rest Off in both readings

The 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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_hover_rest, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_hover_rest, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.227 →

Feedback