GitHub makes Copilot cloud sessions resumable across its website and mobile app

GitHub began rolling out resumable cloud Copilot sessions to paid users.

GitHub began rolling out its connected Copilot cloud experience to users on paid Copilot plans on October 28. The release lets developers start a cloud session on GitHub or GitHub Mobile and continue work from other supported clients. A developer can move from a conversation about a repository to a request for a code change in the same session. The announcement describes separate controls for permissions and the choice of execution environment. [GitHub changelog](https://github.blog/changelog/2026-10-28-work-from-anywhere-with-a-new-connected-copilot-cloud-experience/)

The session moves across clients while the code runs in an environment

GitHub says a session uses a GitHub-managed cloud sandbox by default. Snapshots allow it to resume later from another surface. Teams that rely on Actions-based self-hosted runners or repository setup instructions in `copilot-setup-steps.yml` still need an Actions environment for those sessions. Developers can also register an environment by running Copilot CLI on a machine or virtual machine they control.

That distinction changes what an administrator tests. A session may be easy to resume on a phone while its actual development environment still needs package access, network rules and a reproducible setup. A team can start with a repository task that has a known test command, resume it from another client and check where the tool ran and what state carried over. A clean handoff should preserve enough context for a reviewer to understand the proposed change.

Compute and permissions remain visible decisions

GitHub said cloud sandbox billing would begin in November and draw on a shared Actions compute entitlement. Standard runners and sandbox use draw from the same allowance at their respective rates. Larger hosted runners participate for Team and Enterprise Cloud. A team comparing the new workflow should look at total compute across all of those paths and confirm the billing cycle and applicable plan.

Administrators can control access through the Copilot in the cloud policy. GitHub says earlier repository exclusions carry over, organization sessions remain subject to single sign-on and repositories without write access stay read-only. Those controls determine which tasks can move from chat into a proposed change and make a suitable starting point for a restricted rollout. [GitHub rollout and policy details](https://github.blog/changelog/2026-10-28-work-from-anywhere-with-a-new-connected-copilot-cloud-experience/)