{"version":"2.1.282","anchor":"stopping-an-mcp-task-now-notifies-its-worker","canonical_anchor":"stopping-an-mcp-task-now-notifies-its-worker","heading":"Stopping an MCP task now tells the task's worker it was stopped","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/stopping-an-mcp-task-now-notifies-its-worker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Stopping an MCP task now tells the task's worker it was stopped\n\nStopping a running MCP task now tells the worker behind it that it was stopped, instead of only marking the task as killed\n\n**Unclear.** It is not clear what the worker does when it is told the task was stopped.\n\n**What**\n\nAn MCP task is a longer-running job handled through an MCP server (Model Context Protocol, the standard Claude Code uses to connect to outside tools). When you stop one that is running, Claude Code now tells the worker carrying out the task that it was stopped. Before, the task was only marked as killed. If sending that notice fails, the stop still goes ahead.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}