Source Intelligence
Follow Discord

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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Session state moves onto a pluggable storage backend

Under the hood
Useful2 Signal3
Sessions

Session history, resume and usage can now read from a pluggable backend, though files are still used.

A storage backend handle is threaded through session persistence, but nothing supplies a backend by default.

/usage
What

A storage handle is now threaded through most session persistence paths, so session data can come from a backend rather than files. Nothing supplies such a backend by default in this build.

Details
  • The storageV5 handle is { backend, key } and reaches session log reading, resume, transcript hydration, /usage, the daemon supervisor and prompt history.
  • Task lists can now be read and deleted through the backend's key/list API with namespace: "task" instead of only via files.
  • v5Read records mtimes for files read that way.
  • Falls back to the existing filesystem paths when no backend is supplied.
Evidence

storageV5

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.221 →