Copilot for JetBrains adds model defaults and MCP startup controls
GitHub’s October 10 update to Copilot for JetBrains lets enterprise administrators choose a default agent model and lets users stop MCP servers from starting automatically for Copilot and Claude. The release also requires JetBrains IDE 2025.2 or later.
A starting model developers can change
GitHub’s managed settings reference describes the model setting as the starting choice for a new conversation. Developers can select a different model for an individual conversation. Administrators can name a specific model or use auto selection, and enterprise team mappings can specialize the configuration.
The distinction matters when a company wants a consistent starting point without forcing every task through the same model. An administrator’s preferred default leaves room for a developer to make a different choice for a particular job. The reference also recommends the top level model key. It retains the older permissions.model location as a fallback when that key is absent.
The deployment guide describes a repository chosen by the enterprise for distributing configuration. Those settings apply to people who receive their Copilot license from the enterprise or its organizations, even if they cannot access that repository. GitHub recommends limiting changes to administrators and AI managers while allowing members to see the configuration.
JetBrains appears among the supported clients, but the guide warns that support varies by property. Teams should check the relevant client and setting before carrying a configuration across editors. Documentation for a permission rule or sandbox option elsewhere in Copilot does not establish that it works in the JetBrains plugin.
Tool startup sits beside existing access policies
MCP connects Copilot to tools and context outside the conversation. The JetBrains setup guide supports both remotely hosted servers and local processes, which can reach resources on the developer’s machine. Configured servers expose tools in the chat interface.
Organizations already have a separate policy governing MCP use for their Copilot Business and Enterprise license holders. That policy must be enabled before those users can use MCP. GitHub says this organizational policy does not govern MCP access through personal Free, Pro, Pro+ or Max subscriptions.
The newly announced startup switch controls when configured servers become active. GitHub does not describe it as revoking credentials or changing an organization’s MCP policy.
Diagnostics and the upgrade requirement
A new Fix action in diagnostic menus opens inline chat to request a repair. It uses agent mode where available and ask mode otherwise. Conversation controls also gain turn navigation and actions for editing or copying user messages.
Microsoft’s September 15 support notice had already told JetBrains 2025.1.x users to plan an upgrade. It explains that ending support does not immediately disable an installed Copilot plugin. Existing installations are expected to keep working, but that IDE series stops receiving supported plugin improvements and fixes.
The notice sets 2025.2.x as the minimum and recommends 2026.1 or later. For a managed development team, checking the IDE version comes before planning a plugin rollout. Someone still using 2025.1 needs an IDE upgrade to return to the supported path. A working older installation should not be confused with continuing support.
ByteForward reviewed the announcement and documentation without installing or testing the release. The announcement omits a plugin version, and we could not verify one from the Marketplace listing.
Related coverage examines Google’s Gemini Code Assist sales changes.
Archival software development illustration from 2012. Typing computer screen reflection by Almonroth via Wikimedia Commons. Original photograph and website crops licensed under CC BY SA 3.0. Website layouts may crop the photograph.
