{"version":"2.1.288","anchor":"task-stop-for-unknown-id-can-name-a-host-tool","canonical_anchor":"task-stop-for-unknown-id-can-name-a-host-tool","heading":"Stopping an unknown task can now name the host tool it needs","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/task-stop-for-unknown-id-can-name-a-host-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Stopping an unknown task can now name the host tool it needs\n\nWhen Claude Code can't find a task you ask it to stop, the error may now name the host tool that owns it\n\n**Unclear.** It is not clear when the host-tool lookup is on or what the \"needs\" part of the message names.\n\n**What**\n\nA task is a piece of work Claude Code runs in the background. If you try to stop a task Claude Code cannot find, it used to show a generic not-found message. When a lookup for host tools is on, the message now reads `Task <id> needs <x>: \"<hostName>\".` and names the host that owns the task.\n\n**Why**\n\nThe message points you to where the task lives instead of only saying it was not found.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}