Author: Nadali. Prepared using AI.
On October 28, 2026, GitHub announced a move from included Actions minutes to a shared monetary compute allowance. The new cloud Copilot experience rolls out to paid plans from that date; the company announced cloud sandbox billing for November without specifying a day.
Who benefits
Business owners whose contractor maintains a website or application in GitHub. The practical change: an AI-credit budget does not cover every cost of executing the work.
Two separate accounts of usage
According to billing documentation, cloud sandboxes meter compute, allocated memory and saved snapshots separately. Stopping a session stops compute and memory metering, but snapshot storage remains metered until deletion. A Bundled AI credits budget does not control sandboxes: use a product or SKU budget.
The included allowance is shared by standard hosted runners for private or internal repositories and sandbox compute and memory. On Team and Enterprise Cloud it also covers available larger runners. It is not a separate free quota for each tool.
Before the next bill
Our editorial recommendation:
- Ask the contractor to identify the payer and execution environment for each task.
- Check AI-credit and cloud sandbox budgets separately.
- Agree who monitors the shared allowance and saved sessions. Do not delete needed results merely to save money.
- Check the setting that stops usage at the budget limit, not just notifications.
Access and limits
Copilot documentation confirms dependence on a paid plan and organization policies. Copilot Free retains the older chat; having an included compute allowance does not establish access to the new environment.
The takeaway: agree both budgets before starting cloud tasks. We have not verified the exact November charging date or actual bills. This reports announced changes, not our own savings test.
Related: automation credit limits.
Sources read October 28, 2026. The cover is a reused conceptual AI illustration, not GitHub’s interface.
