A developer works at a laptop as glowing AI, cloud, and security interfaces connect across devices.
GitHub's Ignite-timed update for Copilot in JetBrains is a big one. It adds a cloud sandbox, remote chat access, browser control and on-device voice dictation. It also tightens enterprise defaults and ends support for an older IDE line. The important part is which features are live and which are previews. Several of them need an opt-in, a policy change or a newer IDE.

A developer works at a laptop as glowing AI, cloud, and security interfaces connect across devices. The headline features (all in public preview)​

Cloud sandbox. The JetBrains plugin listing describes it as support for running Copilot sessions in a remote sandbox environment, in preview. GitHub's changelog says the sandbox is an isolated, GitHub-hosted environment, not your own computer. Copilot can change code and run commands and tests there. That frees local resources and allows parallel sessions. GitHub is rolling it out in phases, so don't be surprised if it hasn't reached your account yet. The changelog doesn't publish resource limits, supported repository types or sandbox configuration options.

The isolation is the point. A sandbox session shouldn't be able to read or change files on your machine, and you shouldn't assume it can.

Remote access. You can opt in to make JetBrains Copilot chats available in other Copilot clients, such as VS Code and the Copilot app. You can then discover shared sessions from remotely accessible computers, or reopen remote sessions from history and carry on the conversation. This is also a phased rollout. The plugin's release notes describe it as registering with Mission Control while the IDE is open, so chats can be exposed remotely. In practice, the IDE has to stay open for those chats to be reachable.

Remote access and cloud sandbox are easy to confuse:

  • Remote access exposes a chat running in your JetBrains IDE to other clients.
  • Cloud sandbox moves the execution itself onto GitHub's infrastructure.

On Business and Enterprise plans, expect administrators to control whether remote access is available. GitHub's earlier remote-control announcement for Copilot CLI said administrators must enable remote control and CLI policies for those plans. I'd expect similar gating here, but that's an inference. This changelog doesn't name a policy.

Browser use. Paired with GitHub Copilot in Chrome, the built-in browser-use plugin can open and navigate pages, read their content, and interact with links, buttons and forms. To turn it on in JetBrains, go to GitHub Copilot > Chat > Enable Browser Use. You'll also need the Chrome extension.

This is the feature to treat with the most care. An agent that clicks through forms in a browser where you're already signed in can change real data. Give it narrow, unambiguous instructions and review what it did, especially for anything that writes data or affects other people.

On-device voice dictation. You can dictate chat messages on supported native plugin packages with Editor Preview enabled. You opt in and download a model. The transcript stays an editable draft until you press Send, so a misheard "drop table" won't fire on its own. The changelog doesn't list the supported packages, model size or languages.

Split-mode remote development​

Copilot now supports JetBrains split mode. Chat and editor UI run on your local client, and Copilot operations run on the remote backend. Install the Copilot plugin on both the local client and the remote backend. Otherwise you'll get a half-working setup.

One caveat from the plugin's marketplace page. A user comment there says the plugin doesn't work for remote development since IntelliJ/PyCharm 2026.3. That is a user remark, not GitHub guidance. If you're on very new split-mode builds, test before you roll anything out to a team.

Everyday workflow changes​

Most of the small items are quality-of-life fixes:

  • Timestamps now appear on agent prompts and responses.
  • Delete sits beside Archive in session history. You can also skip future single-session delete confirmations.
  • Steer and queue: Enter steers a running agent session. Ctrl+Enter (Command+Enter on macOS) queues a follow-up. If you're used to Enter meaning "send a new message", retrain your fingers.
  • Copilot Fusion is pinned at the top of agent model management and stays enabled even if you deselect the whole model group.
  • Inline chat shows model names and per-response token details, and keeps the agent-session credit totals. Ask-mode footers show the selected Fusion tier, not the underlying model. The model picker stays open when you toggle Fusion.
  • Quota dialog: Copilot Access usage now looks like other organization plans. It shows organization help links, not upgrade or overage actions.
  • Worktree names: Copilot worktree directories and branch names are shorter and keep their timestamps.

Reliability fixes​

GitHub lists improvements to chat persistence, startup and recovery, and says saved history is preserved. It also lists these fixes:

  • proxy-related loading problems
  • saved Claude Code paths on Unix
  • clearer errors for failed tool calls
  • historical session diffs on newer JetBrains EAP builds
  • context search, code formatting, input focus and MCP sign-in recovery

These are release-note descriptions. GitHub gives no plugin build number and no measurements. If you work behind a corporate proxy, the proxy loading fix is the one to check first.

Admin and governance changes​

  • Providers: Enterprise-managed settings now disable Claude and Codex unless an administrator policy allows an exception. Users' saved provider preferences are preserved. If your developers suddenly can't reach those providers in the IDE, check policy first.
  • Fusion defaults: Copilot Fusion applies enterprise-managed tier defaults. Available tiers stay selectable, and saved choices are kept.
  • Code review: It now uses the Copilot agent review engine. Results still show in the existing inline review interface, so the experience looks the same while the engine underneath changes.
  • Onboarding: The chat onboarding tour is generally available to eligible users. Usage tips are on by default, and a saved tips preference is left alone.

The changelog doesn't name the administrator setting or the default tier values.

Java and Maven​

Java modernization findings now appear in the Problems View on supported IDEs. GitHub doesn't say which IDEs are supported.

Automatic Maven vulnerability checks are back. Opening or importing a Maven project sends dependency coordinates to GitHub Advisories to check for known vulnerabilities. Security teams should note that this means project dependency data leaves the machine. The changelog doesn't detail exactly which coordinates are sent. If you're in a regulated or air-gapped environment, confirm this against your data-handling policy.

Compatibility: check your IDE version​

Support for JetBrains IDE 2025.2 has ended. Move to 2025.3 or later to keep receiving Copilot updates. GitHub recommends 2026.2 or later for the best experience.

Some versions in this story are easy to mix up:

  • 2025.3 is the minimum to keep getting Copilot updates.
  • 2026.2 or later is the general recommendation.
  • 2026.1 or later is the version GitHub's IDE documentation gives for agent sessions in split mode, according to the research notes behind this story.

What to do now​

  • Check your IDE version and upgrade if you're on 2025.2 or earlier.
  • Update the GitHub Copilot plugin. If you use split mode, update it on the backend as well.
  • Try cloud sandbox and remote access when they reach your account. They're phased, so they may not appear yet.
  • Enable Browser Use only when you need it, and review what the agent does.
  • Admins should review provider policy for Claude and Codex, and decide on remote access and Maven advisory lookups.
  • Send feedback through the in-product options or the GitHub Copilot for JetBrains IDEs issues repository.

Bottom line​

JetBrains users are getting the same multi-surface, agent-first Copilot experience VS Code users have had. Sessions can move between clients, run in a sandbox, and drive a browser. These are public previews, and GitHub gives no resource limits or plugin build number. The practical risks are browser actions, the phased rollout, and the Maven dependency lookups. Test in a non-critical project first.


Update: Copilot browser extension adds Edge support and isolation controls (November 18, 2026)​

According to Neowin, GitHub Copilot’s browser extension now supports both Google Chrome and Microsoft Edge, expanding the browser-use preview beyond the Chrome-focused setup described earlier.

The report adds two implementation details that matter for security reviews: Copilot browser tasks run in an isolated tab group, and users can adjust the extension’s permission level in settings. Those controls may help limit the scope of browser automation, but they do not eliminate the need to review actions involving authenticated sites, forms, or sensitive data.

Neowin also reports that the extension is available through the Chrome Web Store and Microsoft Edge Add-ons store. Browser access remains disabled by default and still requires an explicit enablement step in Copilot or another supported client.

 

References

  1. GitHub Copilot in JetBrains, Ignite releases GitHub Changelog 2026-11-17T18:00:59+00:00
  2. GitHub Copilot can now click buttons and fill out forms in your browser Neowin 2026-11-18T17:46:02+00:00
  3. Remote control for Copilot CLI sessions now generally available on mobile, web, and VS Code - GitHub Changelog github.blog