Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Session StateArea: what it touches
Internal ChangesKind: in v2.1.228,
Internal ChangesSection of the release
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.
