Under the hood
Useful3 Signal4
A new storage backend now runs through hundreds of paths, from plugin installs to worktree cleanup.
What's wrong with this entry?
Anonymous. No account, no email.
What
A new storage backend, previously used at a handful of call sites, is now passed into hundreds of functions covering plugin install and update, marketplace refresh, settings writes, task and daemon state, transcript reads, MCP auth caching and worktree cleanup. A new React context supplies it via SessionServicesProvider and useSessionServices.
Details
- Every consumer keeps a branch for when no backend is supplied, falling back to the existing filesystem paths, so behaviour is unchanged without one.
- The provider's default value is an empty frozen object.
- No flag turns this on; the backend is handed down from above, and undefined means the old paths.
- Occurrences rise from 37 in v2.1.226 to 689 here.
Evidence
SessionServicesProvider: () => uNr
Strings lifted out of the shipped bundle, so the claim above can be checked against them.