Web fetch and user context caches are now per session, so forked sessions no longer share them.
What's wrong with this entry?
User context, the cache-breaker, the WebFetch cache and prompt-cache-break state all moved from process-wide memoized storage onto per-session state, so forked and concurrent sessions no longer share them.
- The settings-change subscriber now clears context through the session-aware path rather than emptying a global cache.
- WebFetch results live in a
WebFetchCacheentry in tool state instead of a module-level map. - Prompt-cache-break state sits in a per-source map with a flag recording whether hydration was attempted.
WebFetchCache
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