{"version":"2.1.248","anchor":"an-in-memory-storage-backend-is-bundled-but-off-by-default","canonical_anchor":"an-in-memory-storage-backend-is-bundled-but-off-by-default","heading":"An in-memory storage backend is bundled but off by default","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/an-in-memory-storage-backend-is-bundled-but-off-by-default","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### An in-memory storage backend is bundled but off by default\n\nA full in-memory storage backend ships, off unless you set an environment variable.\n\n**What**\n\nA complete in-memory version of the new v5 storage backend now ships as its own chunk: a tree of directory, value and stream nodes with appends, tombstones, record replacement, leases, change subscriptions, scope listing and deletion, and per-log-channel byte budgets. Whether any of it is used depends on the `CLAUDE_CODE_HOVER_REST` environment variable, or otherwise the `tengu_hover_rest` flag, whose compiled fallback is off.\n\n**Details**\n\n- Versions are strings shaped `s<epoch>.<generation>.<seq>`.\n- Construction is wrapped in a guard that reports success or a `fell_back` outcome and, on failure, drops back to the legacy storage path.\n\n**Evidence**\n\n`v5 in-memory storage backend construction failed; this worker keeps no storage backend`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Internals\n- Names: `CLAUDE_CODE_HOVER_REST`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}