{"version":"2.1.287","anchor":"cloud-sessions-background-commands-recorded-on-the-host-ne","canonical_anchor":"cloud-sessions-background-commands-recorded-on-the-host-ne","heading":"Computers serving cloud sessions now track and can stop their background commands","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cloud-sessions-background-commands-recorded-on-the-host-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Computers serving cloud sessions now track and can stop their background commands\n\nBackground commands that cloud sessions start on your machine are now recorded, listed, capped and can be stopped with a new command\n\n**Unclear.** It is not clear what decides whether this feature is available.\n\n**What**\n\nYour computer can do work for a Claude Code session that runs in the cloud. When it does, any background commands that cloud session starts on your computer are now recorded on your computer. A background command is one that keeps running while the session moves on. Claude Code can now:\n\n- list those background commands\n\n- stop one when asked\n\n- cap how many can run at once\n\nClaude is told that the cloud session is not notified when such a command finishes. Claude Code also prints how to stop one: `claude daemon remote-control stop-shell <id>`.\n\n**Why**\n\nCommands started from a cloud session can keep running on your own machine. You now have a way to see them and stop them.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}