Source Intelligence
Follow Discord

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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Clearer account of a tool call interrupted by an MCP disconnect

You'll notice
Useful4 Signal2
MCP

When an MCP server drops mid tool call, you now see whether the call ran instead of ambiguity.

What

When 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.

Details
  • The spinner line reads Reconnecting to ${e} to learn what happened to the call…, with the server name filled in.
  • One outcome states the call "did not run. It is safe to retry."
  • 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.
  • No flag found; this rides the existing MCP reconnect path. None of these strings exist in v2.1.241.
Evidence

this is the recorded result, the command was not run again

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.242 →