{"version":"2.1.323","anchor":"killing-an-mcp-task-now-records-a-cancelled-outcome-and-noti","canonical_anchor":"killing-an-mcp-task-now-records-a-cancelled-outcome-and-noti","heading":"Stopping an MCP task now tells anything waiting that no result will follow","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/killing-an-mcp-task-now-records-a-cancelled-outcome-and-noti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Stopping an MCP task now tells anything waiting that no result will follow\n\nWhen an MCP task is stopped, Claude Code now records it as cancelled so anything waiting on it stops waiting\n\n**What**\n\nAn MCP task is a longer job run by an MCP server, an outside tool Claude Code connects to. When you or the connected app stop one, Claude Code now:\n\n- Records the task as stopped.\n\n- Confirms any pending updates about the task.\n\n- If something is checking on the task, writes a cancelled outcome saying it was stopped and no result will follow.\n\nThe message also warns that the MCP server may already have done some of the work, or may still finish it. If confirming the updates fails, the stop carries on.\n\n**Why**\n\nA stopped task no longer leaves something waiting for a result that will never arrive.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}