Agent, MCP and interface caches now die with the session instead of lingering in the process.
What's wrong with this entry?
Agent definition loading, MCP connection, tool, resource and prompt caches, task-list watching, teammate mode snapshots, telemetry header caching, output path bindings, fleet roster and editor state, artifact stop latches and voice level smoothing all moved out of module globals. These caches are now discarded with their session rather than surviving for the life of the process.
agentDefinitions
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