{"version":"2.1.290","anchor":"remote-background-tasks-dialog-handles-a-gone-cloud-worker-a","canonical_anchor":"remote-background-tasks-dialog-handles-a-gone-cloud-worker-a","heading":"Remote task list warns when the cloud session may have stopped","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/remote-background-tasks-dialog-handles-a-gone-cloud-worker-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Remote task list warns when the cloud session may have stopped\n\nThe background tasks dialog for cloud sessions now warns when the cloud worker is gone and blocks the stop key in that state\n\n**Unclear.** It is not clear what marks the worker as gone or whether this applies to every cloud session.\n\n**What**\n\nWhen you work with a cloud session (Claude Code running on a remote machine rather than your own), the Background dialog lists the tasks running there. Before, its subtitle always read \"Running in the cloud session\" and pressing `x` always tried to stop the selected task.\n\nNow, when the remote worker is reported as gone:\n\n- the dialog shows \"The cloud session may have stopped, and its tasks too\"\n\n- the `x` stop key does nothing\n\nClaude Code also records two usage events: one when the dialog is shown and one when a stop is unavailable.\n\n**Why**\n\nIf the remote machine has stopped, a stop request cannot reach it. Blocking the key and showing the warning keeps you from pressing stop and assuming it worked.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}