About managing cloud sandboxes
Cloud sandboxes don't have their own access setting, and you can't opt out of them separately from Copilot policies. Copilot uses a cloud sandbox when a member starts a cloud session from any Copilot client. To manage cloud sandboxes, you control access to those features with Copilot policies, and you control spending with budgets.
For more information about cloud sandboxes, see About cloud sandboxes for GitHub Copilot.
Controlling who can use cloud sandboxes
If members get Copilot through your organization or enterprise, the Copilot in the cloud policy controls whether they can run Copilot agents in a cloud environment that GitHub manages, from any Copilot client. The policy is enabled by default. When the policy is disabled, Copilot can't create cloud sandboxes for those members.
- To set the policy for an organization, see Managing GitHub Copilot in the cloud for your organization.
- To set the policy for an enterprise, see Managing GitHub Copilot in the cloud for your enterprise or organization.
Controlling spending on cloud sandboxes
To monitor and limit cloud sandbox spending, set a budget for cloud sandbox usage. You can create a budget for all cloud sandbox usage or for a specific cloud sandbox SKU. See Billing for cloud and local sandboxes for GitHub Copilot.