GitHub's Copilot app now lets developers wrap local repository and working-tree sessions in a sandbox that restricts filesystem access, network calls, and credential exposure on a per-project basis. The feature entered public preview on September 23, 2026, according to GitHub's changelog. It applies only to local sessions, not cloud-run ones, and it ships off by default.
That default is the part product and design leads should sit with. A security control that exists but requires opt-in protects almost no one on day one. Teams that assume Copilot sessions are now contained by default will be wrong unless someone actively flips the setting per project, which means the real rollout question is adoption, not capability. Engineering leads should check whether their organization can enforce the sandbox centrally or whether it depends on individual developers remembering to enable it project by project.
GitHub's announcement does not say whether enforcement can be set at the org or enterprise level, nor does it specify what happens to an in-progress session if sandboxing is toggled mid-task. Those are the operational gaps that matter most before any team treats this as a compliance control rather than a convenience. The changelog confirms scope: filesystem, network, and credentials, tied to local repo and working-tree sessions. It does not confirm performance overhead, platform availability beyond the app itself, or how sandbox violations are surfaced to the user.
The mechanism is straightforward enough. Local sessions mean Copilot is operating directly on a developer's machine, with access to whatever that machine can reach, including internal networks and stored credentials. Sandboxing narrows that blast radius per project, which matters most for anyone running Copilot against repositories that touch sensitive infrastructure or secrets. Without it, a misbehaving or manipulated session has the same reach as the developer running it. With it, that reach is supposed to be scoped down to what the project actually needs. Nobody outside GitHub has stress-tested that boundary yet.
For design leads, the interface question is whether per-project toggling is visible and legible enough that developers treat it as a habit rather than an afterthought. A setting buried two menus deep gets ignored. One surfaced at project creation gets used. GitHub has not detailed where the toggle lives in the app's UI, so that remains an open implementation detail worth checking directly in the preview build.
Security and platform teams evaluating this now have a narrow but concrete task: test whether sandboxing can be mandated at the org level before trusting it as a baseline. Until GitHub confirms that path, the feature is a developer-level opt-in, not a policy.