Counters and latches now belong to a session rather than the whole process.
What's wrong with this entry?
Mutable state that lived in process-wide variables now hangs off a single per-session object, so counters and latches belong to a session rather than the process.
- New domains alongside the existing ones include cost ledger, model selection, request journal, prompt assembly, session flags and scratch, surface capabilities, turn budget, user presence, hook registry, MCP session wiring, invoked skills, identity and conversation latches.
- Accessors for total token and line counters, refusal-fallback model latches, prompt id and index, and approved MCP servers now read from these stores.
- Sessions forked for a different project keep sharing the root's stores, so behaviour should be unchanged.
promptAssembly
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