GitHub Copilot in JetBrains: Split Mode Remote Development Support

GitHub CopilotView original changelog

GitHub Copilot now supports JetBrains split mode remote development. Chat and editor UI run on the local client while Copilot operations run on the remote backend. The Copilot plugin must be installed both locally and on the remote backend.

Key Takeaways

  • Copilot now supports JetBrains split mode remote development.
  • Chat and editor UI stay on the local client.
  • Copilot operations run on the remote backend next to the code.
  • The plugin must be installed on both the client and the backend.
  • It shipped in the November 17, 2026 JetBrains plugin update.
  • It complements the update's remote access and cloud sandbox features for working away from the local machine.

Copilot in JetBrains Split Mode

GitHub Copilot for JetBrains now supports split mode remote development. In this setup, the chat and editor interface run on the developer's local client, while Copilot's operations run on the remote backend where the project lives.

Requirements

The GitHub Copilot plugin must be installed in both places: locally on the client and on the remote backend. Without both installations, Copilot will not work across the split. The support shipped in the November 17, 2026 JetBrains plugin update.

Copilot in JetBrains Supports Split Mode Remote Dev | Yet Another Changelog