Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

One MCP tool-call route no longer asks servers to run the call as a background task

One route for MCP tool calls now always makes a plain call instead of asking the server to run it in the background

You'll notice Removed
JSON All of v2.1.296
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
RemovedKind: in v2.1.296,
RemovedSection of the release

Unclear Whether MCP servers still receive background-task tool calls through the remaining mechanism, and under what conditions, is not settled.

What

MCP (Model Context Protocol) servers are outside programs that give Claude Code extra tools. In one of the places where Claude Code calls an MCP tool, it no longer has the option of asking the server to run the call as a background task. That option used to track the task, watch it, and tell Claude "Running in background; you'll be notified when it completes." That place now always makes an ordinary tool call and waits for the answer.

A separate background-task mechanism for MCP tool calls is still present in another part of Claude Code.

Why

This matters mainly to people who build MCP servers: one older route for background tool calls is gone, so a server should not rely on receiving background-task requests from it.

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 doubtWhether MCP servers still receive background-task tool calls through the remaining mechanism, and under what conditions, is not settled.

See this entry in the whole of v2.1.296 →

Feedback