Under the hood
Useful1 Signal1
Session state variables were gathered into containers so a session resets as a unit.
What's wrong with this entry?
Anonymous. No account, no email.
What
Dozens 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.
Details
- transcript and session state now exposes fields such as the session isolation latch and agent name, and methods including
clearInternalEventWriterandsetRemoteIngressUrl - 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
Evidence
clearInternalEventWriter
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state