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.122 Home All releases ←olderv2.1.121 v2.1.123newer→
Claude Code v2.1.122

MCP Long-Running Task Tracking

What

Adds infrastructure to track, poll, persist, and resume MCP tasks that run asynchronously on MCP servers using the experimental tasks API.

Details
  • When a tool call spawns an MCP task, Claude Code now registers it in a task registry and polls the server for status updates
  • Task metadata is persisted to disk at <session-dir>/mcp-tasks/mcp-task-<id>.meta.json so tasks survive session restarts
  • On resume, previously-running MCP tasks are reconnected to their servers and polling resumes
  • Task status updates (completed, failed, cancelled) are injected back into the conversation as task-notification messages
  • The status bar shows 1 MCP task (or similar) during active polling
  • Supports kill/cancel from the client side
Evidence

Full task lifecycle management (search for "mcp_task", "restoreMcpTasks", "removeMcpTaskMetadata", "Task was cancelled by the server.")

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