{"version":"2.1.242","anchor":"clearer-account-of-a-tool-call-interrupted-by-an-mcp-disconn","canonical_anchor":"clearer-account-of-a-tool-call-interrupted-by-an-mcp-disconn","heading":"Clearer account of a tool call interrupted by an MCP disconnect","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/clearer-account-of-a-tool-call-interrupted-by-an-mcp-disconn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Clearer account of a tool call interrupted by an MCP disconnect\n\nWhen an MCP server drops mid tool call, you now see whether the call ran instead of ambiguity.\n\n**What**\n\nWhen the connection to an MCP server drops mid tool call, Claude Code now says what became of that call instead of leaving it ambiguous. You get a spinner while it reconnects to find out, a plain statement when the call never ran, and a note when a reply arrives afterwards.\n\n**Details**\n\n- The spinner line reads `Reconnecting to ${e} to learn what happened to the call\u2026`, with the server name filled in.\n- One outcome states the call \"did not run. It is safe to retry.\"\n- A late reply after reconnect is labelled as the recorded result of the original call, making clear the command was not executed a second time.\n- No flag found; this rides the existing MCP reconnect path. None of these strings exist in v2.1.241.\n\n**Evidence**\n\n`this is the recorded result, the command was not run again`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}