Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

MCP connections are dropped when you switch accounts mid-operation

You'll notice
Useful3 Signal2
MCP

MCP servers no longer stay connected with the previous account after you switch accounts.

What

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.

Details
  • 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.
Evidence

Account changed while connecting; reconnect to use it

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.238 →