{"version":"2.1.238","anchor":"mcp-connections-are-dropped-when-you-switch-accounts-mid-ope","canonical_anchor":"mcp-connections-are-dropped-when-you-switch-accounts-mid-ope","heading":"MCP connections are dropped when you switch accounts mid-operation","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-connections-are-dropped-when-you-switch-accounts-mid-ope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP connections are dropped when you switch accounts mid-operation\n\nMCP servers no longer stay connected with the previous account after you switch accounts.\n\n**What**\n\nConnect, reconnect, deferred-connect and re-authentication all record which signed-in account they started under and refuse to deliver results after a switch, so a server no longer ends up connected with the previous account's credentials.\n\n**Details**\n\n- A connection that opens during a switch is detached and closed, and its row becomes a failed client with error code `IDENTITY_CHANGED`.\n- In-flight tool calls abort, and re-auth promises created under the old account are refused rather than joined.\n- Cached discovery rows are purged or refused on an identity change.\n- The branches specific to the MCP discovery cache only run when that cache is enabled, which it is not by default; the identity fencing itself is unconditional.\n\n**Evidence**\n\n`Account changed while connecting; reconnect to use it`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}