GitHub Copilot plugin for JetBrains adds new settings and ends support for JetBrains IDE 2025.1
The GitHub Copilot plugin for JetBrains now requires JetBrains IDE 2025.2 or later. The update allows company administrators to set the default model, disable automatic startup of MCP servers, and open an inline chat with a request to fix a diagnostic issue.
The update to the GitHub Copilot plugin for JetBrains ends support for JetBrains IDE 2025.1. Using the plugin now requires JetBrains IDE 2025.2 or later.
Through managed settings, company administrators can select any available GitHub Copilot assistant model as the default for new conversations. The user's explicit choice in the model picker is preserved. A new setting also allows administrators to disable automatic startup of MCP servers for GitHub Copilot and Claude.
The diagnostics menu now includes a Fix action that opens an inline chat with a request to fix the issue. It uses agent mode if available, otherwise ask mode. According to GitHub, the update also improves reliability when switching models and providers, configuring MCP, and working with worktrees.
Why it matters
A newer IDE is required to continue using the plugin. The new controls let administrators determine when configured MCP tools are activated and pass a diagnostic issue to the assistant directly from the IDE menu. However, opening a request for a fix does not in itself establish that the proposed change is correct.
Two audiences, two different impacts
What this means
For individuals
A developer using JetBrains IDE 2025.1 needs to upgrade to version 2025.2 or later to continue using the plugin.
For a business
Administrators can centrally set the model employees use to start new conversations. However, the setting preserves their explicit choice of another model, so it does not restrict them to a single permitted model.
DevelopmentCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.