The News, Explained
GitHub announced an update to Copilot for JetBrains IDEs on October 10, 2026. It covers the model that starts a new enterprise conversation, the path from an IDE diagnostic to a proposed fix, and whether configured MCP servers start automatically. GitHub also changed chat and account workflows and raised the minimum supported JetBrains IDE version. Source
Enterprise administrators can use managed settings to choose any available Copilot agent model as the default for new conversations. This aligns the model initially selected when a member of the organization starts a chat. The explicit model picker remains available to the user. The change should therefore be read as a starting default, not as a policy that locks every conversation to one model. Source
JetBrains diagnostic intention menus now include a Fix action. Selecting it on an IDE error or warning opens inline chat and asks Copilot to repair the issue. Copilot uses agent mode when that mode is available and ask mode otherwise. The shorter path removes the need to copy a diagnostic into a separate chat, but a build and tests are still needed to determine whether the proposed change fixes the issue without breaking other behavior. Source
A new setting also controls MCP server startup. MCP is a standard interface that lets an AI system connect to external data and development tools. Users can stop configured MCP servers from starting automatically for Copilot and Claude. This gives teams a way to activate a server only when it is needed instead of assuming that registration should make the tool active whenever the IDE opens. The announcement does not describe the detailed default value or the full scope of organization-level enforcement for this setting. Source
Everyday chat and account handling changed as well. Signed-in Copilot accounts have clearer names and status displays, navigation works better for long account lists, and a Switch Account action is available. Chat messages are grouped by turn with controls for moving between turns, and users can copy or edit messages they sent. GitHub also updated first-use guidance, the sign-in screen, and cancellation during browser authorization. Source
GitHub says the release improves reliability during language-server startup, model and provider switching, MCP configuration, customization refreshes, file changes, and worktree workflows. At the same time, support for JetBrains IDE 2025.1 has ended. The Copilot plugin now requires JetBrains IDE 2025.2 or later. The announcement does not provide a per-product and per-operating-system version matrix for every fix. Source
OYOPICK’s Take
The important shift is less about adding another model and more about making defaults and tool activation visible. An enterprise starting model with an explicit user override can balance a shared cost or performance baseline with task-specific choice. Organizations should still distinguish a default model from an enforced model in their guidance so members understand what they can change.
The MCP startup control also makes tool activation more predictable. When a development tool can reach repositories, issues, or databases, registering a server and deciding when it runs are separate decisions. A team rollout should record server startup, authentication, tool calls, and shutdown on a representative project before expanding access, especially when connected tools carry meaningful permissions.
Moving directly from a diagnostic to an AI-proposed fix can reduce repetitive work, but removing one warning is not proof that the program remains correct. We hope inline fixes develop as a way to make causes and tests easier to understand rather than replacing review. Organizations that must remain on IDE 2025.1 need a compatibility test and IDE upgrade plan before adopting the latest plugin.