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
HomeReleasesv2.1.221entry #210

Claude Code v2.1.221 ·

Session state moves onto a pluggable storage backend

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

Under the hood Nothing to try yet In Development
JSON All of v2.1.221
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.221,
In DevelopmentSection of the release

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

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.

Read from
Names in the bundle/usage

See this entry in the whole of v2.1.221 →

Feedback