Caches now live per session, so parallel sessions in one process stop contaminating each other.
What's wrong with this entry?
Caches that were previously process-wide now live in a per-session store: the WebFetch URL and domain-check caches, the send-file duplicate set, Bash working-directory tracking, the alias-probe fired set, plus per-host containers holding plugin sync state, the keybinding writer, the diagnostics manager and the binary-check cache. In a process running more than one session at once (SDK, runner, cowork) these no longer bleed across sessions.
- The store is created with the session context and carried through context construction, forking and agent spawn.
- Disposing a session installs a fresh store rather than clearing shared maps.
toolState: this.toolState, toolState
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state