Newsbite analysis · Programming, Tools
GitHub Blog
Local sandboxing in the GitHub Copilot app
GitHub Copilot has introduced local sandboxing to its app, a feature designed to minimize the risks associated with unintended commands by limiting access to system resources. Users can configure sandboxing on a per-project basis, enabling selective access to files, network connections, and credentials. By default, sandboxing is turned off, but can be activated from the app settings. This feature is currently in public preview, indicating that it may evolve based on user feedback and performance. Importantly, while local sandboxing enhances security for local sessions, it does not extend to cloud sandbox sessions, ensuring a clear distinction in environments.
ExperimentConfidence: HighShort term horizonStory: First report
EvidenceOfficial announcementNo quotes
Published 23 Sept 2026, 15:45 UTC1 min read
Lead image — GitHub Blog
Brief
NewsBite reading:GitHub Copilot app adds local sandboxing feature
TL;DR
- Local sandboxing limits access to files, network resources, and credentials.
- Feature configurable per project within the GitHub Copilot app.
- Sandboxing is off by default but can be turned on in settings.
- Existing sessions do not inherit sandbox settings unless restarted.
- Local sandboxing is in public preview and may change.
Interesting facts
- The effective policy may be more restrictive depending on enterprise settings.
- Users can enable sandboxing for active sessions using a specific command.
What changed
The GitHub Copilot app has added a local sandboxing feature to enhance security during development.