{"version":"2.1.221","anchor":"session-state-moves-onto-a-pluggable-storage-backend","canonical_anchor":"session-state-moves-onto-a-pluggable-storage-backend","heading":"Session state moves onto a pluggable storage backend","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/session-state-moves-onto-a-pluggable-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Session state moves onto a pluggable storage backend\n\nSession history, resume and usage can now read from a pluggable backend, though files are still used.\n\n**What**\n\nA storage handle is now threaded through most session persistence paths, so session data can come from a backend rather than files. Nothing supplies such a backend by default in this build.\n\n**Details**\n\n- The `storageV5` handle is `{ backend, key }` and reaches session log reading, resume, transcript hydration, \/usage, the daemon supervisor and prompt history.\n- Task lists can now be read and deleted through the backend's key\/list API with `namespace: \"task\"` instead of only via files.\n- `v5Read` records mtimes for files read that way.\n- Falls back to the existing filesystem paths when no backend is supplied.\n\n**Evidence**\n\n`storageV5`\n\n- Area: Sessions\n- Names: `\/usage`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}