{"version":"2.1.227","anchor":"per-session-state-moved-into-state-container-objects","canonical_anchor":"per-session-state-moved-into-state-container-objects","heading":"Per-session state moved into state-container objects","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/per-session-state-moved-into-state-container-objects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Per-session state moved into state-container objects\n\nSession state variables were gathered into containers so a session resets as a unit.\n\n**What**\n\nDozens of module-level variables holding session state were replaced by fields on singleton container objects, so a session's state is now reset as a unit rather than one variable at a time. No behaviour changes.\n\n**Details**\n\n- transcript and session state now exposes fields such as the session isolation latch and agent name, and methods including `clearInternalEventWriter` and `setRemoteIngressUrl`\n- the old catch-all app-state object was renamed, and its init JSON schema, scheduled-tasks flag and prompt cache allowlist moved to dedicated modules\n\n**Evidence**\n\n`clearInternalEventWriter`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}