Unclear It is not clear what stopping an agent that has already finished but is still viewable now does.
What
The background tasks dialog lists work running behind the conversation and lets you stop it. Its Stop action has changed.
- 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. - Stop now also works on local agents that are no longer running but can still be viewed.
- 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.
Why
Stopping 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear what stopping an agent that has already finished but is still viewable now does.