MCP state, bundled skills, keybindings and the command classifier became singletons you can reset.
What's wrong with this entry?
Dozens of loose module-level variables and cached closures were replaced with singleton class instances, covering MCP connection state, bundled skills and builtin plugins, browser-extension state, keybindings, the package-manager detector and the Bash command-prefix classifier. Most now expose reset() or invalidate(), which changes when caches clear rather than what you see.
- MCP state now carries reconnect, toggle, disabled and policy handling plus a
skippedDynamicServerslist in one place. - Also folds in the remote-settings barrier, the
/dev/ttystdin override and style-key recording.
skippedDynamicServers
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