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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Interrupting an MCP tool call now says the call may have run anyway

You'll notice
Useful4 Signal2
MCP

Interrupting an MCP call now warns you it may have run on the server anyway.

What

An MCP call aborted mid-flight used to come back as an empty error. It now returns a result marked as interrupted with text warning that the call may or may not have completed on the server and should be verified before you assume it did not.

Details
  • The aborted path previously returned no content and only an error flag; it now returns content plus both interrupted and isError.
  • Both MCP client paths check the interrupted flag after a call and raise that dedicated message rather than a generic failure.
  • Downstream rendering uses the flag to separate a user interruption from a tool failure.
Evidence

The tool call was interrupted before a result was received. It may or may not have completed on the server, interrupted: !0, isError: !0

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