Source Intelligence

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.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

MCP long-running task support is compiled in but never requested

Not switched on
Useful2 Signal5
MCP Notable

Full support for long-running MCP server tasks is compiled in but never actually requested.

Task registration, a background driver, placeholder results and a progress poller all exist, but the check that requests a task always returns false.

What

The MCP tool-call path gained a full implementation of long-running server tasks: registering or adopting a task, a background driver, a placeholder result while work continues, and a poller that reports progress as Task <id> .... None of it runs, because the check that decides whether to ask a server for a task is compiled to always return false and the request is sent with no task option set.

Details
  • The task pathway also threads a "tasks not allowed" parameter through the call and its retry-after-auth path.
  • The error map for listing tools learned a new case for pagination limits being exceeded, list_pagination_exceeded.
  • Treat this as landed but inert; nothing in this build asks a server for a task.
Evidence

buildSep2663PlaceholderResult

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