GitHub Copilot CLI brings agentic modes and remote sessions to JetBrains IDEs
GitHub has introduced Copilot CLI integration for JetBrains IDEs, adding ask, plan, and agent modes for automating development workflows, plus a remote session feature that lets developers continue an IntelliJ session from a mobile device via QR code.
Score breakdown
The remote session feature extends an active IntelliJ coding session to a mobile device without interruption, while the new debug logs and token visibility give developers direct insight into how Copilot's agentic decisions are made.
- 01Copilot CLI is selectable as the agent provider inside JetBrains IDEs after installing the latest GitHub Copilot release.
- 02Three modes are available: ask, plan, and agent — demonstrated with a Spring AI application and an Azure deployment workflow.
- 03In plan mode, Copilot presents multiple options and gives a recommendation rather than choosing automatically.
GitHub's walkthrough video introduces Copilot CLI integration for JetBrains IDEs, accessible after installing the latest Copilot release. Users select "Copilot CLI" as the agent provider and can then move between three modes: ask mode for querying the codebase (demonstrated by identifying how to start a Spring AI application via Maven and Spring Boot, including detecting required environment variables), plan mode for generating multi-step strategies (demonstrated by planning an Azure deployment with multiple options and a recommended choice), and agent mode for executing the approved plan with automatic model selection.
Token quota and usage are now visible directly in the interface, removing the need to manage tokens manually.
The update adds several operational improvements. Token quota and usage are now visible directly in the interface, removing the need to manage tokens manually. A `compact` command helps clear the context window during longer conversations. Agent customization is available through Copilot settings, where built-in agents can be edited or new ones added. Debug logs in the Copilot CLI option expose the exact prompts used, token counts, tools called, and the model selected when using auto mode — viewable per individual prompt.
A standout new capability is remote sessions: users enable the feature in settings, run `/remote on`, and scan a QR code with a phone to gain full remote control of the IntelliJ environment from a mobile device. Tasks can be assigned from the phone and results appear in the desktop IntelliJ session in real time. The host computer must remain on and network-connected, and the connection is scoped to the session and device with no data shared without consent.
Key facts
- 01Copilot CLI is selectable as the agent provider inside JetBrains IDEs after installing the latest GitHub Copilot release.
- 02Three modes are available: ask, plan, and agent — demonstrated with a Spring AI application and an Azure deployment workflow.
- 03In plan mode, Copilot presents multiple options and gives a recommendation rather than choosing automatically.
- 04Token quota and usage are now visible in the interface, and a `compact` command manages context window size during long sessions.
- 05Agent debug logs show prompts, token counts, tool calls, and model selection per individual prompt.
- 06A remote session feature lets users run `/remote on`, scan a QR code, and control their IntelliJ environment from a mobile device.
- 07The remote connection is scoped to the session and device; the host computer must stay on and connected to the network.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content. Last processed Jun 19, 2026 · 10:25 UTC. How this works →