Under the hood
Useful1 Signal2
Another batch of shared caches, including rate-limit backoff and sandbox state, became per session.
What's wrong with this entry?
Anonymous. No account, no email.
What
MCP connection caches, agent background-signal resolvers, GitHub rate-limit backoff, the tool memory directory, the correspondent and rename registry, deduplication sets for telemetry, terminal setup state and sandbox and proxy caches all became containers created on demand per session.
Evidence
return adw.of(Pr().host);
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