Storage and session handles are now passed around explicitly instead of read from process-wide state.
What's wrong with this entry?
Config writes, transcript appends (custom title, agent name, PR link, last prompt), session-start and setup hook dispatch, background housekeeping, plugin marketplace operations and many dialogs now receive the storage handle and session object as arguments rather than reaching for process-wide state. Hook dispatch in particular changed shape to take the session plus a storage field.
storageV5: t.storageV5
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