On October 10, 2026, GitHub shipped a new version of its Copilot extension for JetBrains IDEs. Three changes stand out for teams that configure their development machines: a setting to take back control of MCP server startup, a fix action triggered straight from the editor’s diagnostics, and a higher minimum IDE version.
A setting to take back control of MCP server startup
Until now, MCP servers configured in the extension started automatically whenever a project opened. The update introduces a setting that turns this off by default: declared tools stay idle until the developer explicitly activates them for the current session. The change follows on from the MCP specification stabilized in July, which already tightened the protocol’s startup and authentication rules.
In practice, an MCP server wired to an internal ticketing system, a documentation repository, or a deployment service no longer runs in the background the moment the IDE opens. For an organization running several MCP servers across its developer machines, that shrinks the default active surface without blocking occasional use.
A Fix action straight from diagnostics
The intention menus attached to IDE diagnostics (the red or yellow underlines in the editor) now include a Fix action that opens inline chat and asks Copilot to repair the flagged issue. The action uses agent mode when available, and falls back to ask mode otherwise. The stated goal is to shorten the distance between spotting an error and resolving it, without leaving the editing flow.
Default models enforced by administrators
Organizations can now set a default agent model for new conversations through managed settings. Users can still pick a different model for a given session, but the starting point is now defined at the company level rather than shipped as-is by the vendor.
| Change | Before October 10 | Since October 10 |
|---|---|---|
| MCP server startup | Automatic when the project opens | Can be disabled, activated on demand |
| Fixing a diagnostic | Copy the error into chat manually | Fix action in the intention menu |
| Default agent model | Left to each workstation | Can be enforced via managed settings |
| Minimum JetBrains version | IDE 2025.1 supported | IDE 2025.2 or later required |
On a workstation already configured with several MCP servers, the new setting shows up in the extension’s settings:
{
"github.copilot.chat.mcp.autoStart": false,
"github.copilot.chat.mcp.servers": {
"internal-docs": { "command": "npx", "args": ["mcp-server-docs"] },
"ticket-tracker": { "command": "npx", "args": ["mcp-server-tracker"] }
}
}
Turning off automatic MCP server startup turns an always-on toolset into one you switch on when you actually need it.
The update raises the minimum version to JetBrains IDE 2025.2. Workstations still on the 2025.1 branch lose access to the extension’s new features until the IDE itself is updated.
What to take away
The October 10 update does not change what Copilot for JetBrains fundamentally is, but it shifts the dial toward more control: explicit MCP startup, a default model set by administrators, and a fix shortcut that stays optional. Teams running several MCP servers across their workstations should check this setting before it becomes the default on a future release.
On the development machines I set up for client work, MCP servers that start themselves on launch have always been irritant number one, especially when they depend on network authentication that slows down opening a project. This setting, even if it arrives late, fixes a real ergonomics and security gap: a tool that only runs when you call it is easier to audit than one running silently in the background — Simon Janvier.
Further reading: GitHub’s official changelog covers every fix and improvement in this release.
