MCP servers no longer stay connected with the previous account after you switch accounts.
What's wrong with this entry?
Connect, 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.
- A connection that opens during a switch is detached and closed, and its row becomes a failed client with error code
IDENTITY_CHANGED. - In-flight tool calls abort, and re-auth promises created under the old account are refused rather than joined.
- Cached discovery rows are purged or refused on an identity change.
- 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.
Account changed while connecting; reconnect to use it
Strings lifted out of the shipped bundle, so the claim above can be checked against them.