{"version":"2.1.287","anchor":"background-task-kill-can-end-with-a-custom-status-and-summar","canonical_anchor":"background-task-kill-can-end-with-a-custom-status-and-summar","heading":"Stopped background tasks can show a status other than killed","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-task-kill-can-end-with-a-custom-status-and-summar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Stopped background tasks can show a status other than killed\n\nA stopped background task can now end with its own status and summary instead of always showing killed and its description\n\n**Unclear.** It is not clear which parts of Claude Code supply a different final status.\n\n**What**\n\nA background task is work Claude Code runs alongside your conversation. When one is stopped, it always ended with the status \"killed\" and its own description as the summary. Now the part of Claude Code that stops it can give a different final status and summary. \"Killed\" and the description are still used when none is given.\n\n**Why**\n\nThis changes how the end of a stopped task can be shown, so a stopped task may appear with a more specific result.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}