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.jsonso 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
/mcp now shows claude.ai connectors hidden by a manually-added server with the same URL, with a hint to remove the duplicate