What GitHub announced

On October 28, GitHub introduced a connected cloud experience for Copilot: a session can start on github.com or a mobile device, then continue in the Copilot CLI, Copilot app, or VS Code. The session preserves its context. Work can also be started from Slack and Microsoft Teams when the integration is configured.

By default, a cloud task runs in an isolated GitHub sandbox. Its state is saved when it stops so work can resume later from another client. At the same time, GitHub is combining Actions compute into a shared dollar-based entitlement. The pool can be used for standard runners, cloud sandboxes, and, on Team and Enterprise Cloud, larger runners. Starting in November, cloud sandbox use will draw from this shared entitlement. Each type of compute continues to have its own published rate.

Where a small team may benefit

The change should make it easier for developers to hand a task between workstations. For example, they can ask Copilot to investigate a bug, continue the investigation in an editor, and then review the proposed change in a pull request. A cloud environment lets the task run without using an employee’s computer. This is useful for teams that already keep their code and tasks in GitHub; a new chat surface does not, by itself, make a development process autonomous.

As additional context, Tom’s Hardware, reporting on a GitHub technical report, described rapid growth in platform activity and commit volume. That is not an explanation for this billing change, but it is a useful reason to treat compute as a budget line rather than a free add-on to a subscription.

What to check before enabling it

  • Record current Actions and Copilot spending, then track how cloud sessions use the shared entitlement.
  • Set budgets and alerts before enabling background tasks or long-running sessions.
  • Check who can start cloud sessions and which repositories, connectors, and MCP servers they can access.
  • Remember that a session without write access is read-only, and organizations can restrict Copilot through policy.

Limitations

The new experience is available on paid Copilot plans; availability depends on the plan and organization policies. A cloud sandbox is not a replacement for GitHub Actions: it does not support self-hosted runners or Actions-specific environment setup steps. GitHub also warns that Copilot code can contain errors and vulnerabilities, so generated changes still need review and testing.

For a small-team owner, the practical point is to check more than seat-license prices before adding Copilot to new development stages: review the shared compute allowance, budgets, agent permissions, and the cost of maintaining generated code.