Under the hood
Useful2 Signal4
Process-wide caches moved per session, groundwork for several sessions sharing one process.
What's wrong with this entry?
Anonymous. No account, no email.
What
The largest change in this release, invisible on its own: dozens of caches and counters that lived once per process now live in a container looked up from the current session. This is the groundwork for more than one Claude Code session sharing a single process without sharing state.
Details
- Affected: the OAuth token refresh cache, the clipboard tool probe, Linux and tmux terminal state, the telemetry interaction sequence counter, the sandbox and monitor socket registry, the git repository cache, and the analytics event ring buffer.
- The holder keys instances off the session object weakly, so they disappear with the session rather than living for the process lifetime.
Evidence
RHb = new en(() => new SOd());
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