{"version":"2.1.227","anchor":"module-level-caches-moved-onto-objects","canonical_anchor":"module-level-caches-moved-onto-objects","heading":"Module-level caches moved onto objects","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/module-level-caches-moved-onto-objects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Module-level caches moved onto objects\n\nMore caches, from the PR poller to the model catalog, became resettable objects.\n\n**What**\n\nA large sweep replaced module-level variables holding caches and one-shot flags with objects and classes exposing named accessors, across config file reading, the Chrome install prompt, the GitHub PR poller, sandbox startup, plugin hook hot-reload, iTerm teammate panes, artifact live subscriptions and the model catalog. Behaviour is largely unchanged; these caches are now per-instance and can be reset.\n\n**Evidence**\n\n`AA.installUpsellBypassSuppressionCounted`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}