Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.288entry #308

Claude Code v2.1.288 ·

Results of MCP tool calls moved to the background now go to a further check

When an MCP tool call is moved to the background automatically, its result text is now handed to another handler on some platforms, with a fallback if that fails

Under the hood Internal Changes
JSON All of v2.1.288
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.288,
Internal ChangesSection of the release
What

MCP tools are extra tools that Claude Code can call from outside servers you connect it to. A call to one of these tools can be moved to the background automatically, so it keeps running while the session carries on. The handling of such a call has changed: on some platforms, Claude Code now passes the call's result text to a separate handler on the machine running Claude Code. If that handler fails, Claude Code falls back to another path.

Why

In practice, results from MCP tool calls that run in the background may now be handled differently depending on the platform. What this extra step does with the result is not clear.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear what the handler does with the result text, which platforms it applies to, and what the fallback does.

See this entry in the whole of v2.1.288 →

Feedback