Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Clearer account of a tool call interrupted by an MCP disconnect

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

You'll notice Improvements
JSON All of v2.1.242
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.242,
What probably matters to youSection of the release
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 →

Feedback