{"version":"2.1.321","anchor":"task-stop-local-bash-shaped-ids-are-not-looked-up-as-agent","canonical_anchor":"task-stop-local-bash-shaped-ids-are-not-looked-up-as-agent","heading":"Stopping a task by a shell-style ID no longer falls back to agent names","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/task-stop-local-bash-shaped-ids-are-not-looked-up-as-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Stopping a task by a shell-style ID no longer falls back to agent names\n\nA stop request for an unknown shell-task-style ID now fails and asks for the agent's task ID instead of matching an agent by name\n\n**What**\n\nWhen a stop request names an ID shaped like a local shell task's ID and no such task exists, Claude Code no longer tries it as an agent's name. The request fails with a message asking for the agent's task ID.\n\nTasks that were killed without you stopping them also get an extra notice.\n\n**Why**\n\nA stop request can no longer end up stopping the wrong agent because its ID happened to look like a name.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}