{"version":"2.1.233","anchor":"mcp-client-and-other-module-globals-move-into-per-key-holder","canonical_anchor":"mcp-client-and-other-module-globals-move-into-per-key-holder","heading":"MCP client and other module globals move into per-key holders","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/mcp-client-and-other-module-globals-move-into-per-key-holder","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### MCP client and other module globals move into per-key holders\n\nMCP client lists and other module globals moved into registries created on first use.\n\n**What**\n\nBoth MCP client modules replaced their module-level set of live clients and their connection caches with a single registry created on first use. Several other module globals, including shell process tracking, path caches and ignore-file state, moved to per-key holders backed by a weak map.\n\n**Evidence**\n\n`aJe().liveClients`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}