GitHub Copilot in JetBrains: Cloud Sandbox Runs Sessions Off Your Machine
GitHub introduced a cloud sandbox for GitHub Copilot in JetBrains IDEs, now in public preview. Copilot sessions run in an isolated, GitHub-hosted environment instead of on the developer's machine, which frees local resources and allows parallel sessions. GitHub is rolling the preview out in phases.
Key Takeaways
- The cloud sandbox runs Copilot sessions in an isolated, GitHub-hosted environment.
- Copilot can edit code and run commands and tests inside it.
- Running off the local machine frees local resources.
- It enables parallel Copilot sessions in JetBrains.
- The feature is in public preview and rolling out in phases.
- It builds on earlier local and enterprise-managed sandboxes for Copilot in JetBrains.
Copilot Sessions in an Isolated Cloud Environment
GitHub added a cloud sandbox to GitHub Copilot in JetBrains IDEs, announced with its Microsoft Ignite releases and available in public preview. Rather than executing on the developer's computer, a Copilot session runs in an isolated, GitHub-hosted environment, where Copilot can make code changes and run commands and tests.
Why It Matters
Moving execution off the local machine frees local CPU and memory, which is useful in heavy JetBrains projects. It also makes it practical to run several Copilot sessions in parallel, since they no longer compete for the same workstation. Isolation also keeps agent-run commands away from the developer's own environment.
Rollout
GitHub is rolling out the cloud sandbox in phases, so not every user will see it immediately. The same release also moved other JetBrains items into preview, such as remote access to chats from other clients, but the cloud sandbox is the headline capability for JetBrains users.