Under the hood
Useful2 Signal3
Process-wide state moved onto the session object, the biggest structural change in this build.
What's wrong with this entry?
Anonymous. No account, no email.
What
State that used to live in module-level singletons now hangs off the session object, so two sessions in one process no longer share it. No behaviour change on its own, but it is the largest structural change in this release.
Details
- The session object previously carried only workflow usage consent; it now owns a dozen stores, including observers, shell and command history, pending hints, prompt suggestions, plugin sync, precompute, tool progress throttling and the stash of pending write permissions.
- Forked sessions share these stores with their root session rather than getting fresh copies.
- Hundreds of call sites now take an explicit session parameter; for example the pending-write-permission stash is reached through the session rather than a global.
Evidence
writePermissionStash
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