More scattered state became resettable holders, including per-instance locks instead of one global.
What's wrong with this entry?
Dozens of scattered module-level variables, maps and sets were moved into lazily created state objects reached through accessors, covering plugin state, agent and task state, git scrub paths, config caching, teammate mailboxes and terminal capability probes. Several holders gained a reset() method, and a process-wide promise-chain lock became a factory producing per-instance locks, so in-process state can now be torn down and rebuilt.
- MCP errors are now dispatched into a store as
{ type: "mcpError", serverName, error }rather than accumulated in a module array. - New named fields include
agentTranscriptSubdirs,bareGitRepoScrubPaths,installedPluginsFile,terminalRejects,childProcessTmpDirMemoandscriptCapsLatched. - No user-visible behaviour change.
bareGitRepoScrubPaths
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