A dozen caches now hang off the session and are inherited when a session forks.
What's wrong with this entry?
The session object used to carry one field and now carries a dozen, including observers, fallback history, prompt suggestions, pending hints, plugin sync, tool progress throttling, stashed write permissions and the autonomous loop preamble. Each is inherited from the root session when a session forks.
- This is why hundreds of call sites in this area gained a session argument, including observer pairing, auto-mode classifier telemetry, marketplace and plugin cache invalidation, hook registration and transcript sharing.
- These caches are no longer shared between sessions running in the same process.
sessionRefsGate
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