{"version":"2.1.229","anchor":"caches-moved-from-module-globals-onto-the-session","canonical_anchor":"caches-moved-from-module-globals-onto-the-session","heading":"Caches moved from module globals onto the session","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/caches-moved-from-module-globals-onto-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Caches moved from module globals onto the session\n\nWeb fetch and user context caches are now per session, so forked sessions no longer share them.\n\n**What**\n\nUser 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.\n\n**Details**\n\n- The settings-change subscriber now clears context through the session-aware path rather than emptying a global cache.\n- WebFetch results live in a `WebFetchCache` entry in tool state instead of a module-level map.\n- Prompt-cache-break state sits in a per-source map with a flag recording whether hydration was attempted.\n\n**Evidence**\n\n`WebFetchCache`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}