{"version":"2.1.295","anchor":"background-task-stop-for-local-agents-handles-more-cases","canonical_anchor":"background-task-stop-for-local-agents-handles-more-cases","heading":"Stopping background agents and MCP tasks from the tasks dialog is reworked","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/background-task-stop-for-local-agents-handles-more-cases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Stopping background agents and MCP tasks from the tasks dialog is reworked\n\nStop in the background tasks dialog now covers more agent states, and a killed `mcp_task` notifies Claude through the shared path\n\n**Unclear.** It is not clear what stopping an agent that has already finished but is still viewable now does.\n\n**What**\n\nThe background tasks dialog lists work running behind the conversation and lets you stop it. Its Stop action has changed.\n\n- For local agents, which are helper Claude instances (subagents) running on your machine, Stop now records that the stop came from the user (`source: \"user\"`). Before, it called a plain stop with no source.\n\n- Stop now also works on local agents that are no longer running but can still be viewed.\n\n- Stopping an `mcp_task`, a task run through an MCP server (an external tool provider), is simplified. When such a task ends with status `\"killed\"`, a notification carrying a note now goes through the same path already used for other task types. Before, only the existing user-stop notification path ran.\n\n**Why**\n\nStopping an agent or MCP task from the dialog may behave differently than before. Claude, the model, is now told when an MCP task you stopped was killed.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}