Two sessions running in one process no longer share caches with each other.
What's wrong with this entry?
A broad sweep replaced caches that were shared across the whole process with ones looked up per host, so two sessions running inside one process no longer share them. Single-host runs behave exactly as before.
- Covers the API key helper cache and its in-flight request, quota fetching, credential ownership, plugin-install listing, subagent token budget accounting, campaign eligibility, the stdin capture buffer, first-paint metrics and several UI stores.
- The subagent token budget became a class with private fields tracking rolled-over context, task budget re-anchoring and cumulative usage.
reanchorTaskBudget
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.236
Process-wide state replaced by per-session containers
Both mention state
-
v2.1.236
Agent, MCP and UI caches scoped per session
Both mention state
-
v2.1.236
The command queue is now passed around instead of being a global
Both mention state