Under the hood
Useful1 Signal4
Several config and session lookups can accept a new storage backend, but none supply one yet.
An optional storage backend parameter is threaded through many call sites, all still defaulting to the filesystem.
What's wrong with this entry?
Anonymous. No account, no email.
What
Gateway 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.
Details
- Uses namespaced keys such as a "gateway-models" cache key and a "computer-use-lock" state key.
- The lock has distinct error paths: an already-exists result means the lock is held, an invalid-argument result is thrown.
- Whether any given call site uses the new backend depends on what the caller passes, which varies across the build.
Evidence
computer-use lock v5 create failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.