Check Whether the GitHub Copilot Local Sandbox Turns On Automatically After General Availability

Which Copilot surfaces can use it?

GitHub's October 7 announcement lists Copilot CLI, the Copilot app, and VS Code sessions that use Agent Host as supported. It is not saying the same setting applies to every session in every IDE. CLI and app settings are managed separately, so turning it on in one does not turn it on in the other. Start by distinguishing the surfaces and session types your team uses.

What does it restrict, and how far does the isolation go?

It controls which directories a command can read and modify, the internet and local network, and access to Git and GitHub CLI credentials. The underlying technology is Microsoft eXecution Container. The official concepts documentation explains that it uses operating-system-level restrictions rather than a separate virtual machine or container. The tool execution policy applies regardless of the selected model.

The date checked is 2026-10-10. Do not assume this one setting also limits the permissions an external server holds.

What policies should I decide before turning it on?

Try writing down write permission for the working repository and read permission for reference material separately. If package installation is needed, check which hosts it will connect to, and set apart any task that needs to reach config files or personal files outside the repository. At first, confirm with a small task that both file edits and the necessary network traffic work, and it will be easier to find the cause of any block.

Is the cloud sandbox also generally available?

No. The same documentation marks the cloud sandbox as a public preview. The local one is included with Copilot at no extra cost, while the cloud one is billed by usage. When you change where things run, check availability status and cost together.