{"version":"2.1.287","anchor":"gh-stand-in-dir-hook-and-background-shells-for-served-tools","canonical_anchor":"gh-stand-in-dir-hook-and-background-shells-for-served-tools","heading":"Cloud-served shell commands can run in the background","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/gh-stand-in-dir-hook-and-background-shells-for-served-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud-served shell commands can run in the background\n\nShell commands run for a cloud session can now be told to run in the background, and a GitHub CLI stand-in folder option is added\n\n**Unclear.** It is not clear what the `gh` stand-in folder is used for.\n\n**What**\n\nWhen your machine runs shell commands on behalf of a cloud session, those commands can now be told to run as background shells, which keep going while Claude carries on with other work. Claude Code's configuration also gains an option for a stand-in folder for `gh`, the GitHub command-line tool.\n\n**Why**\n\nCommands run for a cloud session can now keep running in the background, as they can in a local session.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}