COPILOT FEATURE MATRIX: WHICH IDE VERSIONS UNLOCK WHAT
GitHub's public-preview Copilot feature matrix clarifies which features are supported across IDEs and versions. VS Code 1.103.0 and Visual Studio 17.14.x enable...
GitHub's public-preview Copilot feature matrix clarifies which features are supported across IDEs and versions. VS Code 1.103.0 and Visual Studio 17.14.x enable Agent mode, Copilot Code Review, MCP, code referencing, and next-edit suggestions; BYOK remains preview in VS Code and is not supported in Visual Studio, and workspace indexing is VS Code-only. JetBrains has most core features (Agent mode, Chat, Code Review, Code referencing, MCP) but lacks workspace indexing; Eclipse/Xcode miss code referencing, and NeoVim is completion-only.
You can standardize minimum IDE versions per team to get consistent Copilot capabilities and avoid fragmented experiences.
It surfaces where regulated/data-sensitive needs (BYOK) and tool integrations (MCP) are ready vs preview so you can plan pilots safely.
-
terminal
Pilot VS Code 1.103.0 with workspace indexing plus code referencing on a large monorepo and benchmark suggestion quality and latency.
-
terminal
Prototype an MCP tool exposing schema/catalog/runbook queries and validate Copilot responses, permissions, and auditability.
Legacy codebase integration strategies...
- 01.
Set enforced IDE baselines (e.g., VS Code ≥1.103.0, Visual Studio ≥17.14.x, JetBrains latest) and disable unsupported features to prevent drift.
- 02.
If you require BYOK, favor VS Code (preview) and avoid Visual Studio for now; scope code referencing to selected services and review data egress.
Fresh architecture paradigms...
- 01.
Default to VS Code devcontainers with Agent mode, Code Review, and workspace indexing enabled, and include prompt files/custom instructions in repo templates.
- 02.
Structure repos and docs for code referencing (clear modules, API specs, READMEs) and build MCP endpoints for internal platforms early.