{"version":"2.1.238","anchor":"mcp-work-aborts-when-the-signed-in-account-changes-mid-fligh","canonical_anchor":"mcp-work-aborts-when-the-signed-in-account-changes-mid-fligh","heading":"MCP work aborts when the signed-in account changes mid-flight","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-work-aborts-when-the-signed-in-account-changes-mid-fligh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP work aborts when the signed-in account changes mid-flight\n\nSwitching accounts would cancel in-flight MCP work instead of finishing it under the new identity, but it's dark.\n\n**What**\n\nClaude Code now refuses to carry MCP tool calls, re-authentication, and reconnects across a switch of the signed-in account, so work started under one identity is never completed under another. A tool call that reaches a re-auth path is cancelled, pending re-auth started under the old account is refused rather than reused, and a reconnect that spans the switch fails and asks you to try again. The whole path depends on an account-change counter that only advances while the MCP discovery cache is on, and that cache is off in this build, so none of it can be observed on a default install.\n\n**Details**\n\n- Aborted tool calls report \"MCP tool call aborted: account changed before reauth\" or the same message ending \"during reauth\".\n- A reconnect interrupted by a switch fails with error code `IDENTITY_CHANGED` and the message \"Reconnect cancelled: the account changed while connecting. Choose Reconnect again.\"\n- Cancelled reconnects are recorded under the telemetry reason `mcp_reconnect_identity_changed`.\n- Purges of the MCP discovery cache on a 401 or 403 response are skipped when the account has already moved on, so stale-credential cleanup does not clobber the new identity.\n- A guard on disabled servers rides on the same counter and is likewise inert here.\n- Turn the path on by setting the `MCP_DISCOVERY_CACHE` environment variable to true, or by receiving a server value for the `tengu_mcp_discovery_cache_enable` flag; with neither, the strings ship but never appear.\n\n**Evidence**\n\n`Reconnect cancelled: the account changed while connecting. Choose Reconnect again.`, `mcp_reconnect_identity_changed`\n\n- Flag `tengu_mcp_discovery_cache_enable`: Not enough to say (read for one account on one subscription tier against v2.1.238; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}