Local sandboxing is generally available in GitHub Copilot for JetBrains IDEs
GitHub announced the general availability of local sandboxing in GitHub Copilot for JetBrains IDEs. Agent tools and commands run on the developer’s computer with access restricted by rules set by the developer or organization.
GitHub announced the general availability of local sandboxing in GitHub Copilot for JetBrains IDEs. Tools and commands initiated by GitHub Copilot run on the developer’s computer with restricted permissions.
The restrictions cover access to files, the network, credentials, and other system capabilities. The rules are set by the developer or their organization. According to GitHub, this creates a security boundary for running agent tasks locally.
Why it matters
When assigning work to an agent, you can also define the permissions for executing its commands. This makes it possible to separate the resources needed for a specific task from other files, network access, and credentials on the computer.
Two audiences, two different impacts
What this means
For individuals
Developers can use rules to limit which resources on their computers agent tools and commands can access.
For a business
An organization can set rules governing access to company files, the network, and credentials for agent tasks; these permissions thus become part of risk management when using GitHub Copilot.
Risks and complianceCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.