Shared process-wide state moved into per-session containers, so parallel sessions stop stepping on each other.
What's wrong with this entry?
Session cost and usage counters, telemetry providers, auth state, prompt-cache-break state, skill health and dump-prompt state moved out of one shared mutable object into classes fetched per host through a WeakMap-backed container with an explicit reset. Several ad-hoc caches, including tool-search descriptions, fetched web URLs and agent definitions, are now class instances cleared through that container.
ToolSearchTool: cache invalidated - deferred tools changed
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