GitHub's new sandboxes matter because they turn secure agent execution from a homegrown platform problem into a default part of the coding workflow.
What Shipped
On June 2, 2026, GitHub moved cloud and local sandboxes for Copilot into public preview. Local sandboxes isolate Copilot-triggered shell execution on the developer machine, and cloud sandboxes launch fully isolated ephemeral Linux sessions through copilot --cloud.
GitHub says local sandboxing is built on Microsoft MXC and can be centrally enforced through Intune or other MDM platforms. Cloud sessions inherit existing Copilot cloud agent policies, which means orgs can apply familiar controls without bolting on a new security layer.
Why This Changes the Tooling Layer
Agentic development stops being a toy the moment the agent can execute commands, modify files, call tools, and interact with the network. That is also the moment the security model gets harder. GitHub is making a direct product bet that isolation should sit inside the default developer experience rather than arrive later as a custom enterprise patch.
That is a structural improvement, not a convenience feature. The execution layer is where trust is either built or lost.
Why Parallel and Portable Sessions Matter
The cloud sandbox story is also about throughput. GitHub says teams can continue sessions across devices and offload compute-intensive tasks without consuming local resources. That matters because persistent autonomous work quickly becomes a scheduling and environment problem, not just a model problem.
Once secure execution is portable, agents can operate more like workers with their own bounded workspace instead of temporary helpers attached to one laptop.
The ZHC Angle
This continues the execution-control story we covered in persistent sandboxes and Warp's multi-harness layer. The frontier is no longer just better code generation. It is better operating envelopes for autonomous code generation.
Zero-human software companies need agents that can act continuously without turning every machine into an unbounded trust exercise. Sandboxes are how that becomes credible.
The Take
GitHub is productizing a simple but important truth: if coding agents are going to run more of the software lifecycle, secure execution environments become foundational infrastructure. This preview moves that layer much closer to default adoption.
Related: See our earlier notes on persistent sandboxes, Warp, and workspace agents.