{"version":"2.1.224","anchor":"storage-backend-plumbed-through-several-call-sites-but-not-s","canonical_anchor":"storage-backend-plumbed-through-several-call-sites-but-not-s","heading":"Storage backend plumbed through several call sites but not switched on","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/storage-backend-plumbed-through-several-call-sites-but-not-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Storage backend plumbed through several call sites but not switched on\n\nSeveral config and session lookups can accept a new storage backend, but none supply one yet.\n\n**What**\n\nGateway model discovery, the computer-use lock, session-store loading of `~\/.claude.json` and user settings, the settings-key presence probe and session transcript lookup all gained an optional new storage backend parameter. When none is supplied, the existing filesystem behaviour runs unchanged, and the computer-use lock call sites in this build supply none.\n\n**Details**\n\n- Uses namespaced keys such as a \"gateway-models\" cache key and a \"computer-use-lock\" state key.\n- The lock has distinct error paths: an already-exists result means the lock is held, an invalid-argument result is thrown.\n- Whether any given call site uses the new backend depends on what the caller passes, which varies across the build.\n\n**Evidence**\n\n`computer-use lock v5 create failed`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}