{"version":"2.1.287","anchor":"daemon-remote-control-remove-reports-background-commands","canonical_anchor":"daemon-remote-control-remove-reports-background-commands","heading":"Removing a remote-control folder now also stops cloud sessions' background commands","tier":"use","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/daemon-remote-control-remove-reports-background-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Removing a remote-control folder now also stops cloud sessions' background commands\n\n`claude daemon remote-control remove` can now stop background commands cloud sessions run in the removed folder and prints a note about them\n\n**Unclear.** It is not clear what condition decides whether the background commands are counted and stopped.\n\n**What**\n\nThe `claude daemon remote-control remove` command takes a folder out of the list a daemon (a Claude Code program running in the background) serves for remote control. It used to print only `removed <dir>`.\n\nIt can now also count the background commands that cloud sessions have running in the removed folder, or in a folder listed after it. It stops the ones this daemon serves and prints a line starting with `note: cloud sessions had`, followed by how many background commands were running. This extra step only runs under a condition Claude Code checks internally.\n\n**Why**\n\nRemoving a folder can now stop work that cloud sessions had running there. Check for running background commands before you remove a folder if you need them to finish.\n\n- Area: Remote Control\n- Names: `claude daemon remote-control remove`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}