{"version":"2.1.236","anchor":"version-5-session-storage-is-decided-once-per-process","canonical_anchor":"version-5-session-storage-is-decided-once-per-process","heading":"Version 5 session storage is decided once per process","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/version-5-session-storage-is-decided-once-per-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Version 5 session storage is decided once per process\n\nWhether the newer session storage is used is decided once at startup and cannot change mid-session.\n\n**What**\n\nThe newer v5 session-storage backend used to be consulted wherever a caller happened to check `tengu_hover_rest` or simply passed a v5 handle. This build reads the flag once at startup and pins the answer, and every v5 path now checks the pinned value too: session file writes, plugin listing, sidecar writes, session-metadata re-append, config backup listing, and skill and plugin existence checks. Passing a v5 handle is no longer enough, and the choice cannot flip mid-session.\n\n**Details**\n\n- The flag falls back to false, so it is off unless remote config turns it on.\n- A later read that disagrees with the pinned value logs a warning and keeps the original decision.\n\n**Evidence**\n\n`tengu_hover_rest read `\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.236; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}