Under the hood
Useful1 Signal1
More globals moved into a per-host object, changing scope when sessions share a process.
What's wrong with this entry?
Anonymous. No account, no email.
What
State that lived in module-level globals now sits in one host-scoped object, which changes how it is scoped when more than one session shares a process.
Details
- Named slots include credential slots, MCP process wiring, request and account-credit latches, telemetry handles, a model strings cache and the settings source, plus session flags, invoked-skill records and conversation latches.
- Call sites for skills bookkeeping, teleported session info, sticky-beta unlatching and startup profiler state were rewritten to read through it.
- No user-visible behaviour change.
Evidence
credentialSlots
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