{"version":"2.1.227","anchor":"a-new-storage-backend-is-being-wired-through-the-whole-cli","canonical_anchor":"a-new-storage-backend-is-being-wired-through-the-whole-cli","heading":"A new storage backend is being wired through the whole CLI","tier":"soon","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/a-new-storage-backend-is-being-wired-through-the-whole-cli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### A new storage backend is being wired through the whole CLI\n\nPlugins, MCP, settings, themes and dozens of screens now accept the new storage handle nobody supplies.\n\n**What**\n\nAn 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.\n\n**Details**\n\n- Writes pass a durability hint, either `followAtomic` or `inPlace`.\n- Because of the fallbacks, behaviour with no handle is identical to the previous build.\n\n**Evidence**\n\n`publishDiscipline`\n\n- Area: Storage Backend\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}