Copilot cloud billing, shared Actions compute and the checks for November

The official announcements, product guidance and billing documentation were checked on November 4, 2026. The release announcement describes general availability on paid Copilot plans alongside a rollout starting October 28. The announcement names November without specifying a day for billing to start. Check availability and applicable billing conditions for your account before starting.

Moving between screens is different from changing execution environments

The current concepts page separates client, session and environment. This helps distinguish continuing work on a phone from where the commands actually run.

Cloud is the default where the new environment choice is offered, but the documentation says defaults can vary by workflow. Opening work on the web or a phone does not by itself identify the compute being used. Check the session's selected environment.

Cloud sessions can be shared and resumed across supported surfaces. The current comparison describes GitHub Actions-based sessions as available on the GitHub website. The release announcement also says that existing Actions-based self-hosted runners or copilot-setup-steps.yml still require Actions as the environment. Changing clients does not mean every existing environment configuration moves to Cloud.

Copilot access and GitHub included compute are separate

The new connected cloud experience requires a paid Copilot plan and applicable organization and enterprise policies. Copilot Free users are described as continuing with the older Copilot Chat experience on the web and Mobile.

The following is monthly included compute for GitHub account plans, not a Copilot license price list. These USD amounts were displayed in the included-usage documentation checked on November 4.

An amount in the GitHub Free row does not grant access to the new paid Copilot cloud experience. Identify the account plan, Copilot plan and billable owner of the work separately.

What sharing an allowance with Actions means

The current billing guidance says that standard GitHub-hosted runners for private or internal repositories and cloud sandbox compute and memory can draw from the same monetary allowance. Available larger runners can also draw from it for billing accounts on Team or Enterprise Cloud.

The products do not acquire a single common usage unit. Runners and sandboxes retain their own meters and published rates; their calculated costs draw from the monetary allowance. The guidance says no eligible usage type has priority over another.

The allowance resets at the start of the billing cycle. Do not assume that the account's cycle necessarily begins on the first day of a calendar month. The documentation separately identifies standard GitHub-hosted runners for public repositories and self-hosted runners as free usage that does not reduce the allowance. Do not extend that exception to every larger runner or every repository.

Running costs and stopped-session snapshots use different meters

The billing documentation separates three meters. Memory is based on the amount allocated to the session, rather than the amount momentarily in active use.

For an illustration of the calculation, suppose a session with 4 GiB allocated runs for 300 seconds. Compute costs $0.0072; memory costs $0.0036 for 4 × 300 GiB-seconds, giving $0.0108 in total. This calculation covers only compute and memory under that assumption, not snapshot storage. It is not a total session-cost estimate that also includes other items such as AI credits associated with model use.

While stopped, compute and memory are not metered, but the documentation says the resumable snapshot's storage continues to be metered until deletion. Stopping work should not be interpreted as ending every cost. Consider the need to preserve resumable work alongside its storage state. The sandbox items explicitly listed as drawing on included compute are compute and memory; do not assume that a remaining compute balance establishes identical treatment for storage.

Identify the billed account and budget type

Sandbox usage is billed to the account that owns the environment. For work in repositories, the repository owner is billed. For work without a repository, the selected owner is billed; the documentation says a personal account is the default if no owner is chosen. Calling work a team task does not identify which organization will pay.

Cloud compute is separate from AI credits. The billing page specifically says Bundled AI credits budgets do not include cloud sandbox usage. Check a product-level or applicable SKU-level sandbox budget to control that spending.

A budget or alert is not automatically a usage block. The documentation says enabling Stop usage when budget limit is reached blocks additional sandbox usage when the budget reaches 100%. Accounts with a valid payment method may incur additional charges after consuming included usage; without a valid payment method, usage is described as blocked once the quota is exhausted.

Five checks before starting a new session

• Is Cloud selected, or does the task require the existing Actions environment setup?
• Which personal or organization account owns the repositories and the billable sandbox?
• What is that account's billing cycle and remaining included compute amount?
• Which product- or SKU-level sandbox budget applies, and is stop-usage enabled?
• Will a resumable snapshot remain after stopping, and does the work need to be preserved?

Organization cloud policies and repository exclusions still apply. Organization data access must meet SSO requirements, and the documentation describes sessions without repository write access as read-only. Connected surfaces do not remove account permissions or budget boundaries.