{"version":"2.1.235","anchor":"process-global-caches-moved-into-per-host-scoped-containers","canonical_anchor":"process-global-caches-moved-into-per-host-scoped-containers","heading":"Process-global caches moved into per-host scoped containers","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/process-global-caches-moved-into-per-host-scoped-containers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Process-global caches moved into per-host scoped containers\n\nProcess-global caches (API keys, quotas, budgets, UI stores) moved to per-host containers instead of module singletons\n\nA wide mechanical sweep replaced module-level singleton caches with containers looked up per host. This covers the apiKeyHelper cache and its in-flight promise with epoch-based invalidation, quota fetching, credential\/beacon ownership, plugin-install listing state, subagent token budget accounting (now a class with private fields `rollOverContext`, `reanchorTaskBudget`, and `cumulativeUsed`), FotW campaign eligibility, stdin capture buffer, first-paint metrics, and several UI stores.\n\nThe practical effect is that two hosts running in one process, as in fleet or multi-session setups, no longer share these caches. Single-host runs behave the same as before.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}