Under the hood
Useful2 Signal3
Globals became resettable objects, making it possible to restart a session inside a running process.
What's wrong with this entry?
Anonymous. No account, no email.
What
A large mechanical refactor turned dozens of module-level variables into fields on lazily created singleton objects reached through accessors, some with an explicit reset(). Nothing changes for you, but it makes tearing down and restarting a session inside a running process possible.
Details
- Covers the command fuzzy-search index, shell history, sandbox session flags, artifact and workshop state, plugin and marketplace caches, MCP tool-refresh sequences, terminal layout caching (a per-node cached layout instead of a WeakMap) and several event emitters.
- The sandbox reset is async and calls the settings-subscription cleanup.
Evidence
sandboxDisabledThisSession
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