{"version":"2.1.227","anchor":"a-new-storage-backend-is-wired-through-the-product-but-retur","canonical_anchor":"a-new-storage-backend-is-wired-through-the-product-but-retur","heading":"A new storage backend is wired through the product but returns nothing","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-wired-through-the-product-but-retur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### A new storage backend is wired through the product but returns nothing\n\nA new storage layer is plumbed everywhere but builds nothing, so files are still read directly.\n\n**What**\n\nAn 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.\n\n**Details**\n\n- References to the handle grow from 37 to 693 across the bundle, replacing many module-level globals and ambient lookups.\n- Keys look like `{ namespace: \"jobsRoot\", draftKey: ... }`, with namespaces including `state`, `daemon`, `mailbox`, `sidecar` and `fileHistory`.\n- Code paths now branch on the handle, for example writing a job draft through the store rather than creating a directory and a file.\n- The CLI builds the handle once at startup and wraps subcommand handlers so they receive it.\n\n**Evidence**\n\n`storageV5`, `pinStorageV5`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.227; this account: off, anonymous baseline: off, compiled default: off) 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.\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"}