Per-session state is now inherited by forked sessions, so a child no longer overwrites its parent's.
What's wrong with this entry?
State that used to live once per process now lives on the session and is inherited by forked sessions, so a child session no longer shares or overwrites its parent's. This covers observer pairings, the autonomous-loop preamble latch, compaction precompute, the worktree resume refusal, memory sync notices, command history, known Slack channels, and path and directory scan caches.
- Forks read the parent's values through their root session rather than starting empty.
- Post-compaction cleanup and the observer arm and retire helpers now take the session as an argument.
autonomousLoopPreamble
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