{"version":"2.1.323","anchor":"mcp-tasks-service-side-polling-handoff-and-worker-poller-st","canonical_anchor":"mcp-tasks-service-side-polling-handoff-and-worker-poller-st","heading":"Long-running MCP tasks can be handed to a polling service","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-tasks-service-side-polling-handoff-and-worker-poller-st","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Long-running MCP tasks can be handed to a polling service\n\nBackground tasks on MCP servers can now be checked by a separate service, with Claude Code checking once and then waiting for updates\n\n**Unclear.** What decides whether the polling service is used instead of Claude Code checking tasks itself.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools, and some of their jobs run in the background as tasks. Before, Claude Code always checked on these tasks itself. Now a task can be handed to a separate polling service:\n\n- Claude Code checks the task once, then waits for a change notice or a message from you.\n\n- A task can be moved to the background automatically after a wait.\n\n- When you resume a session, these tasks are restored or stopped.\n\n- Records of finished tasks now include a final summary.\n\n**Why**\n\nIt changes how MCP background tasks are followed and how they come back when a session is resumed.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}