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