GitHub Copilot in Visual Studio Gets Usage Alerts, MCP Trust, and C++ GA

GitHub's June 2026 Copilot update for Visual Studio 2026 ships six concrete changes: a real-time usage and billing alert system, fingerprint-based trust validation for MCP servers, general availability of the C++ modernization agent, long-range next edit suggestions, pull request context in Copilot Chat, and a full in-IDE PR review workflow. All features are available to every Copilot plan tier, including the free tier.

What happened

GitHub shipped its June 2026 Copilot update for Visual Studio 2026 on July 14, 2026. The release covers six areas, all framed around giving developers more visibility and control rather than adding raw generation capability.

Feature	Status
Copilot usage tracking and billing alerts	Generally available
MCP server trust validation	On by default
C++ modernization agent (MSVC upgrades)	Graduated from preview to GA
Long-distance next edit suggestions	Opt-in via settings
Pull request context in Copilot Chat	Preview feature flag required
In-IDE pull request review	Generally available

What each feature actually does

Usage tracking and billing alerts

The refreshed Copilot Usage window (Copilot badge menu, then Copilot Usage) reflects Copilot’s usage-based billing model with live updates. Three alert types fire proactively: approaching your limit, hitting your limit, and when overages kick in. You can tune the warning threshold in settings to control how early the notification appears.

MCP server trust validation

MCP (Model Context Protocol) servers let Copilot call external tools. Visual Studio now checks each server’s configuration and asset fingerprint against a trusted baseline at startup. If the fingerprint has changed since you last approved it, a trust dialog blocks the server from running until you review and accept the change. The setting lives at Tools, then Options, then GitHub, then Copilot, then Copilot Chat. It is on by default.

This is a meaningful security addition. Supply-chain attacks on developer tooling are increasingly common, and having the IDE flag configuration drift before execution adds a real check. For teams using AI integration that touches external tool servers, this kind of validation should be part of any deployment checklist.

C++ modernization agent now generally available

The MSVC upgrade scenarios inside the Copilot modernization agent have left preview. Two operating modes are available. Automated mode runs the full upgrade end-to-end. Guided mode pauses before each step so you can review the assessment, the plan, and the execution. Access it by right-clicking a project in Solution Explorer and choosing Modernize, or by typing @Modernize in Copilot Chat.

Long-distance next edit suggestions

Previously, next edit suggestions only looked at code near your cursor. Now they can predict and propose follow-up edits anywhere in the currently open file. Enable it at Tools, then Options, then Text Editor, then Inline Suggestions, and select “Enable extended range suggestions.”

Pull requests in Copilot Chat and in-IDE review

Right-clicking a pull request in the Git Repository window and choosing “Add to Copilot Chat” feeds the PR description, changed files, and comments into the chat context. You can also reference a PR inline by typing # followed by the PR ID. This requires the “View pull requests for a Git repository” preview feature flag to be enabled.

Separately, a new in-IDE PR review experience lets you browse, comment, approve, and complete pull requests from GitHub or Azure DevOps without leaving Visual Studio. The two features pair together: load a PR into the IDE, then pull it into Copilot Chat for triage or summary help.

Why it matters

The billing visibility piece matters most for teams on usage-based plans. Without alerts, developers have no feedback loop until an invoice arrives. The MCP trust layer addresses a real attack surface that has grown quickly as more teams wire AI assistants to external servers and databases.

The C++ modernization GA is notable for shops still running older MSVC codebases. Automated legacy upgrades have historically required dedicated migration sprints. Whether the agent handles project-specific edge cases well enough to skip manual review is the real question, and the Guided mode option suggests GitHub knows the answer varies.

Teams tracking AI coding tool costs will want to check out our coverage of how Microsoft’s study found AI coding agents raise pull request volume by 24%, which puts review tooling improvements like the in-IDE PR flow in useful context.

Our take

The usage alert system is the most practically useful change in this drop. Copilot’s move to consumption-based billing means surprise overages are a real risk, especially on Business and Enterprise plans where multiple seats are generating requests. Getting a configurable threshold alert is basic hygiene that should have shipped with the billing model change.

The MCP trust validation is good to see as a default-on feature, not an opt-in. Most developers will not manually audit server fingerprints, so making the IDE do it automatically is the right design call.

The C++ modernization agent going GA is worth testing on a branch before committing it to production pipelines. “Graduated from preview” does not mean “works perfectly on your specific codebase.” Guided mode is the safer starting point.

If your team is evaluating how Copilot fits into a broader web development or engineering workflow, this update makes the tooling meaningfully more production-ready, particularly on the security and billing sides.

What to do about it

1. Open the Copilot Usage window and set a warning threshold that matches your team’s monthly budget.
2. Verify MCP trust validation is enabled under Tools, then Options, then GitHub, then Copilot, then Copilot Chat.
3. If you maintain a C++ project targeting MSVC upgrades, run the modernization agent in Guided mode on a feature branch first.
4. Enable “Enable extended range suggestions” in Text Editor settings and run it for a week before deciding whether to keep it on.
5. Turn on the “View pull requests for a Git repository” preview feature flag to trial in-IDE PR review.

Start with the usage alert threshold. Everything else is useful, but a surprise overage bill lands first.

Source: GitHub Changelog