{"version":"2.1.238","anchor":"the-v5-storage-choice-reads-the-environment-variable-first","canonical_anchor":"the-v5-storage-choice-reads-the-environment-variable-first","heading":"The v5 storage choice reads the environment variable first","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/the-v5-storage-choice-reads-the-environment-variable-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### The v5 storage choice reads the environment variable first\n\nAn environment variable now takes priority over the server flag when picking the new storage backend.\n\n**What**\n\nThe code selecting the v5 storage backend checks `CLAUDE_CODE_HOVER_REST` before falling back to the `tengu_hover_rest` flag, whose compiled fallback is false.\n\n**Details**\n\n- The variable is propagated to spawned sessions, so a pinned choice is inherited.\n\n**Evidence**\n\n`let e = V.CLAUDE_CODE_HOVER_REST ?? it(\"tengu_hover_rest\", !1);`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.238; 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: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}