COPILOT FEATURES BY IDE/VERSION: WHAT’S GA NOW
GitHub’s Copilot feature matrix clarifies which capabilities are GA vs. preview across IDEs and versions. In the latest releases, VS Code 1.103 and Visual Studi...
GitHub’s Copilot feature matrix clarifies which capabilities are GA vs. preview across IDEs and versions. In the latest releases, VS Code 1.103 and Visual Studio 17.14.x have Agent mode, Copilot code review, code referencing, and MCP available; workspace indexing is VS Code–only, and BYOK/vision remain mostly in preview. JetBrains, Xcode, and Eclipse have partial coverage, with several features still marked preview.
You can plan rollout by matching team IDEs/versions to needed features like agent workflows, repo-aware code review, and monorepo indexing.
Compliance and data controls vary by IDE (e.g., BYOK preview/unsupported in some), affecting governance decisions.
-
terminal
Validate Agent mode and Copilot code review on sample PRs in VS Code 1.103 and Visual Studio 17.14.x; compare defect catch rate and review time vs. baseline.
-
terminal
For monorepos, enable VS Code workspace indexing and measure completion accuracy/latency; pilot MCP integration with internal tools to assess context quality and security.
Legacy codebase integration strategies...
- 01.
Audit IDE and Copilot extension versions; prioritize upgrades to VS Code 1.103 or VS 17.14.x to unlock agent, code review, and code referencing, noting Visual Studio lacks BYOK.
- 02.
Trial .NET/Java Upgrade Agent on a small service to gauge migration quality, CI impact, and rollback strategy before wider use.
Fresh architecture paradigms...
- 01.
Standardize on VS Code 1.103 to leverage workspace indexing and MCP from day one; adopt custom instructions now and pilot prompt files/custom chat modes as they mature.
- 02.
Define governance for preview features (BYOK, vision) and gate them via feature flags until policies and telemetry are in place.