Visual Studio updates GitHub Copilot usage tracking

What happened?

Microsoft has released the June 2026 update for Visual Studio, introducing significant changes in GitHub Copilot integration. The main novelty is a Copilot usage window that displays real-time token consumption, aligning with GitHub's new usage-based billing model implemented on June 1, 2026. Now, instead of counting requests, token consumption is measured, and developers can monitor their position relative to their plan limits directly from the IDE.

Additionally, security has been enhanced with trust validation for Model Context Protocol (MCP) servers, now verified in two stages during startup. The Copilot modernization agent for C++ has also reached general availability, updating projects to the latest version of MSVC Build Tools. Another improvement is the extension of next edit suggestions (NES) to the entire active file, and color emoji rendering throughout the environment.

Why is it important?

The shift to token-based billing represents a change in the economics of AI-assisted development. Previously, developers paid per request, which encouraged intensive use but could lead to unpredictable costs. With the token model, cost is directly linked to processing volume, which may benefit light Copilot users but increase costs for heavy tasks. The real-time usage window is crucial for teams to control spending and avoid billing surprises.

MCP validation addresses an emerging security risk: MCP servers can execute arbitrary code and access data. By verifying the integrity of the server's configuration and capabilities before execution, Microsoft protects developers from potential attacks that maliciously modify tools or instructions.

Copilot improvements, such as long-range editing suggestions, boost productivity by allowing AI to anticipate changes anywhere in the file, not just near the cursor. This can significantly speed up repetitive code writing or refactoring.

What consequences will it have?

For developers, transparency in token consumption will enable better cost planning. Companies with many developers will need to adjust budgets and possibly negotiate custom plans with GitHub. MCP validation may slightly slow server startup but offers a necessary security layer in environments where multiple AI tools are used.

C++ modernization will facilitate migration of legacy projects, reducing technical debt. Color emojis, though seemingly trivial, improve readability of comments and documentation, especially in teams using emojis to mark tasks or bugs.

In the long term, token-based billing could extend to other GitHub and Microsoft products, setting an industry standard. Developers will need to familiarize themselves with metrics like tokens per request and optimize their code to reduce consumption.

What should readers know?

• Accessing the usage window: From the Copilot badge menu, select "Copilot Usage". It shows current consumption and plan limit.
• MCP validation: When starting an MCP server, Visual Studio compares the current configuration with a trusted baseline. If changes are detected, manual review is requested.
• Enabling extended NES: In Tools > Options > Text Editor > Inline Suggestions, check "Enable extended range suggestions".
• Update availability: The June 2026 update is deployed automatically or can be downloaded from the Visual Studio website.

"The June 2026 Visual Studio update not only improves transparency in Copilot usage but also strengthens security with MCP validation and expands productivity capabilities with long-range editing suggestions."

Additional context

Visual Studio 2026 was released in November 2025 as a native AI version. This update consolidates its integration with GitHub Copilot and responds to developer demands for greater control over costs and security. Competition with IDEs like JetBrains and VS Code (which also integrates Copilot) forces Microsoft to differentiate with exclusive features.