Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.227 Home All releases olderv2.1.226 v2.1.228newer
Claude Code v2.1.227

A new storage backend is wired through the product but returns nothing

Not switched on
Useful1 Signal4
Storage Backend

A new storage layer is plumbed everywhere but builds nothing, so files are still read directly.

An optional key/value storage handle is threaded through most of the product; its factory returns nothing even when gated on.

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

An optional storage handle, a namespaced key/value store used in place of direct file reads and writes, is now passed explicitly into settings loading, plugin and marketplace commands, MCP task restore, background and fleet jobs, teammate mailboxes, the LSP manager, transcript reads, migrations, the REPL and most dialogs. Nothing changes on this build: it is built only when the tengu_hover_rest flag is on (default off), and the factory returns nothing even then, so every call site falls back to the existing filesystem path.

Details
  • References to the handle grow from 37 to 693 across the bundle, replacing many module-level globals and ambient lookups.
  • Keys look like { namespace: "jobsRoot", draftKey: ... }, with namespaces including state, daemon, mailbox, sidecar and fileHistory.
  • Code paths now branch on the handle, for example writing a job draft through the store rather than creating a directory and a file.
  • The CLI builds the handle once at startup and wraps subcommand handlers so they receive it.
Evidence

storageV5, pinStorageV5

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.

See this entry in the whole of v2.1.227 →