Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Session StateArea: what it touches
Internal ChangesKind: in v2.1.229,
Internal ChangesSection of the release
What
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.
Details
The settings-change subscriber now clears context through the session-aware path rather than emptying a global cache.
WebFetch results live in a WebFetchCache entry 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.
Evidence
WebFetchCache
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
