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 v5 threading spans the CLI with filesystem fallbacks everywhere and no visible source of a handle.
What
An optional alternative storage handle, referred to internally as storage v5, is now passed into plugin install and marketplace code, MCP server commands, settings writes, session and history reads, daemon and terminal bookkeeping, theme writes, task registries and dozens of UI components. Mentions went from 37 to 689. Every call site still falls back to reading and writing files directly when no handle is supplied, and nothing in the source shows what decides whether a run gets one.
Details
Writes pass a durability hint, either followAtomic or inPlace.
Because of the fallbacks, behaviour with no handle is identical to the previous build.
Evidence
publishDiscipline
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
