Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Start here · Getting started

Check Copilot cloud sandbox billing first

Written November 2, 2026

From November, Copilot cloud sandboxes draw on the same Actions compute pool as your CI. Check the pool, the meter, and the budget stop first.

What changes in November 2026

Cloud sandboxes — the isolated Linux environments GitHub hosts for Copilot cloud sessions — are generally available on paid Copilot plans. Billing for cloud sandbox usage begins in November 2026. GitHub gives a month, not a day, so do not plan around a start date nobody has published. Free usage draws from the shared compute entitlement, and usage beyond that entitlement follows your existing rates, budgets, and payment settings. Billing applies to cloud sandboxing only. Local sandboxing is a separate technology, included in the standard seat at no additional cost, and it is not billed this way.

The model work itself is billed separately. The work a model does draws on AI credits, while a cloud sandbox draws on Actions compute. Copilot's credit cost for model work is a different meter from the sandbox meters below: confusing the two is how a sandbox session looks free until the compute pool runs dry.

The three meters

Cloud sandbox usage is measured on three meters, each with its own published rate:

Compute and memory are not metered while a session is stopped. Snapshot storage is metered from the moment a session stops until the snapshot is deleted — a stopped session is cheap, not free, for as long as its snapshot survives. GitHub's own worked example: 600 seconds with 4 GiB of memory costs $0.0144 of compute plus $0.0072 of memory, $0.0216 in total, deducted from the included compute. That is one short session at a modest size, and it is the right scale to keep in mind: seconds and gibibytes, not minutes and flat fees.

One wording difference to know about: the billing page prices compute per "compute second", while the page describing cloud sandboxes carries the identical rate table with the unit labelled "vCPU second". Same price, different unit word. If you compare the two pages, you are looking at the same $0.000024 rate under two labels.

The shared pool and your plan

The included Actions entitlement is now one shared, dollar-based pool. It covers standard runners, cloud sandboxes, and — on Team and Enterprise Cloud only — larger runners. Each product keeps its own published meter and rate, and no eligible usage type has priority over another when drawing from the pool: a sandbox session and a CI run draw on the same money, first come, first served. The entitlement resets each billing cycle, and GitHub expresses it as a monetary amount, not a quantity of minutes. The included amounts per month are $12 on GitHub Free, $18 on Pro, $12 for free organizations, $18 on Team, and $300 on Enterprise Cloud. Cloud sandbox compute and memory can draw from that pool. If no valid payment method is on file, usage is blocked once the quota is used up.

Steps

  1. Open your usage view and find the pool. Check how much included compute your plan carries this cycle, and how much of it your CI already uses. A sandbox habit that looks small against $300 looks very different against $12.
  2. Read the meter before the session, not after. Decide the session length and memory size up front, and price it at the three rates above. A long session at a large memory size is the expensive shape; a short session at a small size is not.
  3. Set the budget stop before the first session. Budgets can be set at product level and at SKU level, and the "stop usage when budget limit is reached" setting blocks further usage at 100%, with a banner. Set it before running anything: a budget set after the spend is a report, not a stop. Note that cloud sandboxes are not part of the "bundled AI credits" budget type, so a credits budget does not stop sandbox spend.
  4. Delete stopped snapshots you will not resume. Snapshot storage keeps metering from stop until deletion. A session you stopped meaning to resume, then forgot, keeps charging storage for the snapshot.
  5. Check the payment method on file. Without a valid payment method, usage stops when the quota is used up. That is a hard stop in the middle of work, not a warning.

What can go wrong

Limits

Related playbooks

Sources

Back to: Start here · Coding playbooks hub · Also: What an agent costs, in plain figures · Token cost calculator · Copilot's credit cost for model work