What changed
In its October 28, 2026 update, GitHub described a connected Copilot cloud experience: a session can start on GitHub.com, GitHub Mobile, Copilot CLI, the Copilot app, or VS Code, then continue on another surface. Cloud sessions run in an isolated environment managed by GitHub, and their state can be resumed later.
At the same time, GitHub is combining included Actions compute into a shared dollar-based entitlement. It can be spent on standard GitHub-hosted runners, cloud sandboxes, and, on Team and Enterprise Cloud, larger hosted runners. Each product has its own published rate, so the shared dollar balance is consumed at different speeds.
What this gives a team
A useful scenario is assigning an agent a bounded task, starting it in one client, and continuing in another without losing the session. The cloud environment reduces dependence on laptop capacity and separates agent task execution from a developer's local machine.
However, this is not merely an interface convenience: a cloud coding agent accesses a repository and compute, and the new arrangement ties its budget to Actions. Administrators should check:
- whether cloud features are enabled for the relevant plans and users;
- which repositories and actions are permitted by organization policies;
- what budget and notifications apply to the shared Actions pool;
- who can connect tools and context to a session;
- how third-party MCP servers and secrets are controlled.
A practical start
Begin with a test repository and a few tasks that do not require production secrets. Restrict permissions, enable budget alerts, and measure the cost per completed ticket or prepared pull request, including review time. Verify that sessions actually move between the clients the team uses and that the cloud sandbox meets data requirements.
For self-hosted environments, GitHub separately points users to Actions-based runners or registered self-hosted environments; these are not interchangeable with the standard cloud sandbox.
Limitations
The new cloud experience is available only on paid Copilot plans; rollout began on October 28. Sandbox usage is charged against the included Actions entitlement starting in November 2026, with further usage subject to plan, published rates, and overage settings. Cloud environments do not support workflows that require Actions-based self-hosted runners or the copilot-setup-steps.yml environment setup file.
Bottom line
A connected session can simplify work for a distributed team, but economics depend on more than minutes. Before enabling the feature, review cloud-access policies, Actions limits, connected tools, and cost per accepted task.
