Under the hood
Useful1 Signal3
Host-scoped state jumped from two places to fifty-two, isolating sessions sharing a process.
What's wrong with this entry?
Anonymous. No account, no email.
What
State that used to sit in module-level singletons is now looked up per host, covering startup profiling marks, account credit latches, worktree resume refusals and first-party event loggers. Host-scoped lookups go from 2 in the previous build to 52 here.
Details
- Ad-hoc warn-once booleans, such as the one for a malformed remote autocompact frame, moved into a shared claim registry.
Evidence
remote_autocompact_frame_drop
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