Under the hood
Useful2 Signal3
Session identity and working directories now live in one object that can be forked per project.
What's wrong with this entry?
Anonymous. No account, no email.
What
The scattered globals for session id, parent id and working directories were replaced by a single session object that can be subscribed to and updated, with a project fork that keeps the root's identity but overrides directories. Re-identifying through such a fork now throws instead of silently succeeding.
Details
- The settings cache and the CLI launch flags (interactive, print output format, client type, bypass permissions, scheduled tasks, init JSON schema and the rest) were each folded into a class with a
reset().
Evidence
A withProject fork cannot re-identify the session
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