Copilot sessions in JetBrains can now run in a cloud sandbox or follow you to VS Code
GitHub's Ignite update for the JetBrains plugin adds a cloud sandbox, remote session access, browser use and on-device dictation in public preview, and ends support for IDE 2025.2.

GitHub, part of Microsoft, has released a large update to its Copilot plugin for JetBrains IDEs. The headline change is a cloud sandbox that runs Copilot sessions in a GitHub-hosted environment instead of on the developer’s machine. It is in public preview.
The sandbox is one of four public-preview features in the release, alongside remote access to chats, browser use and on-device voice dictation. GitHub is rolling out the sandbox and remote access in phases, so not every account will see them immediately.

A sandbox that frees the laptop and allows parallel sessions
According to GitHub, in the cloud sandbox Copilot can make code changes and run commands and tests in an isolated hosted environment. That frees local resources and lets several sessions run in parallel. Users pick the sandbox from a dropdown in the chat panel.
Remote access is a separate opt-in. Once enabled, Copilot chats started in JetBrains become available in other Copilot clients, such as VS Code and the Copilot app. Users can find shared sessions on computers that allow remote access, or reopen remote sessions from history and carry on the conversation.

Browser use works together with the GitHub Copilot extension for Chrome. The built-in plugin can open and navigate pages, read their content, and interact with links, buttons and forms. It is switched on under GitHub Copilot > Chat > Enable Browser Use.
On-device voice dictation is available on supported native plugin packages with Editor Preview turned on. Users opt in and download a model; transcripts stay as editable drafts until the user selects Send. The plugin also now supports JetBrains split mode remote development, where chat and editor UI run on the local client while Copilot operations run on the remote backend. The plugin must be installed on both sides.

Smaller changes that affect daily use
Several workflow tweaks arrive too. Pressing Enter steers a running agent session, while Ctrl+Enter (Command+Enter on macOS) queues a follow-up. Session history gains a Delete button beside Archive, agent prompts and responses show timestamps, and Copilot worktree directory and branch names are shorter.
Copilot Fusion, the option that lets Copilot pick models for a task, is now pinned at the top of agent model management and stays enabled even if a user deselects the whole model group. For managed enterprise setups, Claude and Codex are now turned off by default, and only an administrator policy can grant an exception.
Code review now runs on the Copilot agent review engine, though results still appear in the existing inline interface. Java modernization findings show in the Problems View on supported IDEs. GitHub also brought back its automatic Maven security scan: when a user opens or imports a Maven project, the plugin sends the project’s dependency identifiers to GitHub Advisories to look for known vulnerabilities.
Support for JetBrains IDE 2025.2 has ended. Users need 2025.3 or later to keep receiving updates, and GitHub recommends 2026.2 or later.
Where JetBrains users now stand against other Copilot clients
The release is mostly about narrowing the gap between JetBrains and the rest of the Copilot family. A separate GitHub post from the same day says browser use in the Copilot app is also in public preview, works in Chromium-based browsers such as Chrome and Edge through the Chrome extension, runs in an isolated tab group, and is off by default. The same feature is listed as available in the CLI, VS Code and JetBrains, so the JetBrains plugin now matches those clients.
The Fusion change ties into a model story. In its Fusion update, GitHub says Copilot Fusion Max reached a 71.2% resolution rate on Terminal-Bench 4.1, 5.4 percentage points ahead of Opus 5.5 and Fable 5.2. Those are GitHub’s own reported figures, and the post does not say whether JetBrains users get every tier. Fusion also sits within a model lineup that changed a day earlier, when we reported that Copilot retired Claude Opus 4.8, Opus 5 and GPT-5.6 Terra from its model picker.
What the changelog leaves unsaid
The post does not say which plans include the cloud sandbox or remote access, how the sandbox is billed, or what limits apply to parallel sessions. It gives no rollout dates beyond “phases”, and no regions. Which plugin packages count as “supported” for dictation is also not spelled out, nor is the size of the dictation model users must download.
Security teams may also note two behaviors: remote access makes local chats reachable from other clients once a user opts in, and Maven projects now send dependency coordinates to GitHub Advisories by default on open or import. GitHub describes both, but the changelog does not detail admin controls for either beyond the enterprise provider policy.
For now, JetBrains users on 2025.3 or later can update the plugin and look for the new options in chat settings. Feedback goes through in-product options or the GitHub Copilot for JetBrains IDEs issues repository.
Sign Up for the Daily AI Pulse
One email a day. All the stories that matter.
By signing up, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.
Leo MartinsAI Tools, Prompts & Practical AI ExpertLeo Martins is the AI Tools & Practical AI Expert at Aiholics, focused on helping readers use artificial intelligence to improve productivity, creativity and everyday work.
You may also like

GitHub Copilot app can now fix your code scanning alerts without leaving it

Copilot code review can now be switched on or off by API, from enterprise down to repo

Copilot lands in Xcode and JetBrains Air, plus Agent Merge in its app
