{"version":"2.1.318","anchor":"background-task-kill-hint-now-depends-on-backend","canonical_anchor":"background-task-kill-hint-now-depends-on-backend","heading":"Ctrl+X hint in background tasks now names a backend-specific action","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/background-task-kill-hint-now-depends-on-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Ctrl+X hint in background tasks now names a backend-specific action\n\nThe ctrl+x hint in the background-tasks panel no longer always says \"delete\"; the action word now depends on where the task runs\n\n**What**\n\nThe background-tasks panel lists jobs Claude Code is running out of view. Pressing ctrl+x acts on the selected job. The word describing that action used to be fixed as \"delete\". It now comes from the job's backend, meaning the place or system that runs it.\n\n- The confirmation hint, which read \"ctrl+x again to delete\", now reads \"stopped \u00b7 ctrl+x again to\" followed by the backend's action word.\n\n- The ctrl+x action label is chosen from the backend by `So(h.state.backend)` instead of being \"delete\".\n\n- The footer hint reads \"ctrl+x to\" plus the backend's word for finished jobs, and still \"ctrl+x to stop\" for running ones. Whether a job can be removed (`canDelete`) also now depends on the backend.\n\n**Why**\n\nFor some kinds of job, \"delete\" was not an accurate description of what ctrl+x does. The hint you see may now use a different word, so read it before pressing ctrl+x a second time.\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"}