{"version":"2.1.232","anchor":"session-state-moved-off-module-globals","canonical_anchor":"session-state-moved-off-module-globals","heading":"Session state moved off module globals","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/session-state-moved-off-module-globals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Session state moved off module globals\n\nLots of session state now belongs to each session, which matters when several run in one process.\n\n**What**\n\nState that was held in module-level singletons is now resolved per host: invoked skills, request latches, startup timing, event-logger state, the session registry, project-directory and temp-directory caches, artifact share probes and the token-reminder state. Behaviour is meant to be unchanged; it matters when several sessions run in one process.\n\n**Evidence**\n\n`memory-watcher: started with the storage interface`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}