You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Background TasksArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release
Unclear It is not clear what marks the worker as gone or whether this applies to every cloud session.
What
When 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.
Now, when the remote worker is reported as gone:
the dialog shows "The cloud session may have stopped, and its tasks too"
the x stop key does nothing
Claude Code also records two usage events: one when the dialog is shown and one when a stop is unavailable.
Why
If 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what marks the worker as gone or whether this applies to every cloud session.