Microsoft shipped the June 9 update for Visual Studio 2026, delivering a trio of features that give developers tighter control over AI consumption, personalization, and compiler toolchain management. The Preview 3 release introduces a native Copilot Usage window, a dedicated Theme Color Editor, and a long-requested cross-installation MSVC toolset discovery mechanism—all available immediately for insiders and early adopters.

This is the second major feature drop since Visual Studio 2026 entered public preview in April, and it addresses some of the most vocal feedback from the developer community. The Copilot Usage meter puts visibility into AI token consumption and quota limits directly inside the IDE, the Theme Color Editor unlocks fine-grained personalization beyond the built-in themes, and the opt-in MSVC discovery allows side-by-side installations to share one copy of the MSVC compiler, saving disk space and simplifying maintenance.

Copilot Usage Window: AI Assist Under a Microscope

From the moment GitHub Copilot was first integrated into Visual Studio, developers asked for a way to track how much they were leaning on the AI pair programmer. The new Copilot Usage window is Microsoft’s answer—a real-time meter that surfaces token counts, daily and monthly consumption, and any active rate limits that apply to an organization’s subscription plan.

Invoked from the View menu or by clicking the Copilot icon in the status bar, the window splits into two tabs: Usage and Limits. The Usage tab shows a rolling 30-day chart of completions, chat turns, and context window expansions, broken down by language. The Limits tab displays the current tier (Free, Individual, Business, or Enterprise) and how close a user is to hitting soft caps—for example, the 2,000 completions-per-month ceiling on the free tier. A percentage bar changes from green to yellow to red as the cap approaches, and an optional reminder can be set to pop up at 80% usage.

For administrators, the pane exposes aggregate data for an entire organization when Visual Studio is connected to a GitHub Copilot license through Entra ID. IT managers can now see which teams are the heaviest AI users without leaving the IDE or querying the GitHub API. Microsoft says the data is cached locally and only transmitted to GitHub when the user explicitly opts into cloud sync, addressing privacy concerns raised during earlier Copilot feedback sessions.

A subtle but welcome addition is the “suggestion quality” indicator—a small thumbs-up/thumbs-down widget that appears next to each completion in the output. Tapping it feeds into a telemetry loop that, over time, should improve Copilot’s inline suggestions for C++, C#, and Python workloads. Developers can disable this feedback mechanism from the Copilot settings page if they prefer to work without sending interaction data.

Theme Color Editor: Total Chromatic Control

Visual Studio has always supported dark, light, and blue themes, plus a handful of community contributions. But fine-tuning individual UI elements—the editor background, line numbers, scrollbar sliders, or tool window borders—required exporting a .vstheme file and manually editing XML tokens. The Theme Color Editor shipped in this update eliminates that friction.

Accessible from Tools > Options > Environment > Theme Color Editor, the new dialog presents a familiar color-picker interface overlaid on a pane-by-pane representation of the IDE. Users can click on any UI region—the text editor, Solution Explorer, the Output window, the tab well, or the status bar—and instantly change its foreground or background color. The editor includes 60 predefined palettes drawn from popular community themes like Dracula, One Dark Pro, and Solarized, with a “customize” button that branches into a full HSB/RGB hex editor.

Changes take effect immediately; there is no longer a need to restart Visual Studio or reload the IDE. The editor saves tweaks as .vstheme files inside the %LOCALAPPDATA%\Microsoft\VisualStudio\17.0\ThemeCache folder and automatically backs up the previous configuration. Teams can export a corporate color scheme and push it via group policy, a capability that enterprise customers have requested for years.

Accessibility is a central design pillar: the editor includes a contrast checker that flags any foreground-background pair that fails WCAG 2.1 AA standards. Keyboard navigation works through all color fields, and a high-contrast-only toggle switches the entire UI to system-defined high-contrast colors while keeping the custom palette for normal mode.

Cross-Install MSVC Toolset Discovery: One Compiler, Many IDEs

Developers who juggle multiple versions of Visual Studio—say, a stable 2022 release alongside the 2026 preview, or a side-by-side with a Game Development workload—have long lamented the duplication of the MSVC compiler toolchain. Each installation pulls its own copy of the C++ libraries, linkers, and compilers, often consuming gigabytes of redundant disk space. The new opt-in MSVC toolset discovery feature lets Visual Studio 2026 detect and use MSVC installations from other Visual Studio versions on the same machine.

When the feature is enabled—through a checkbox in the Installer’s “Individual components” page or via the vswhere command-line utility—the IDE scans known Visual Studio install roots (C:\Program Files\Microsoft Visual Studio\2022\Professional, for example) and registers any compatible MSVC v143 or later toolset. From that point, the C++ project properties page shows a dropdown allowing a developer to select “MSVC v14.42 (from VS 2022 17.8)” alongside the locally installed version.

There are caveats. This is strictly opt-in: the IDE will never automatically consume a foreign toolset without explicit user permission, and each discovered toolset must be manually approved in the Installer. Cross-version debugging is supported only when the remote debugger version matches, and Microsoft warns that mixing library versions can lead to ABI mismatches. The company is working with the vcpkg team to ensure package manifests respect the toolset origin, but for now the feature is recommended primarily for building legacy C++ projects that target an older CRT.

The discovery mechanism relies on the Visual Studio Setup Configuration API, which already powers the Installer’s “modify” experience. When installed, a new COM component—Microsoft.VisualStudio.Setup.Configuration.ToolsetDiscovery—registers itself and periodically checks for newly installed Visual Studio SKUs. The polling interval is once every 24 hours, though a manual refresh button in the IDE’s Tools > Options > Toolset Discovery page forces an immediate scan.

How to Get the Update

Visual Studio 2026 Preview 3 is available now by switching the update channel to “Preview” in the Installer. Users running the current release channel will not see these features until the final 17.12 release, which Microsoft has tentatively slated for August 2026. Because the Copilot Usage window and MSVC discovery touch licensing and system-wide configuration, they are not available in the free Community edition; Professional and Enterprise licenses are required. The Theme Color Editor, however, works across all editions, including the free tier.

The installer payload weighs in at approximately 1.2 GB for a minimal C++ workload; adding the Theme Color Editor component adds 32 MB. Microsoft says that subsequent updates will be incremental through the standard delta mechanism.

Community Reaction

Early feedback from the Visual Studio Developer Community has been broadly positive, with the Copilot Usage window earning particular praise for its transparency. “Finally I can see whether my team is about to hit the cap before the end-of-month scramble,” wrote one enterprise developer on the Microsoft forums. Several users requested the ability to set per-solution usage budgets, and a Microsoft program manager confirmed that it is on the backlog for a future update.

The Theme Color Editor saw immediate adoption by extension authors, who are now packaging their color schemes as one-click .vstheme files. One popular YouTuber demonstrated creating a fully customized catppuccin-inspired IDE in under 90 seconds, a process that previously required editing XML files and multiple restarts.

MSVC discovery drew mixed reactions. “It’s the feature I didn’t know I needed until I saw my C: drive shrink by 8 GB,” commented a C++ game developer. But others pointed out that mixing toolchains can create arcane linker errors, and they urged Microsoft to build a “toolchain verifier” that flags incompatibilities before build. A Microsoft engineer replied that such a verifier is under active investigation.

Under the Hood: How the Features Came to Be

All three additions stem from top-voted Developer Community suggestions. The Copilot Usage request had accumulated 1,200 votes since 2024, and the MSVC discovery idea was a spin-off from a thread about reducing Visual Studio’s disk footprint that dated back to 2021. The Theme Color Editor emerged from a hackathon project inside the Visual Studio team, initially prototyped as a VS extension before being adopted into the core product.

During a Q&A at the Microsoft Build 2026 conference, Visual Studio director Amanda Silver explained that the team prioritized transparency and developer agency this cycle. “When we integrated Copilot, we realized we needed to give users a dashboard that was as reliable as their Azure billing console,” she said. “And the theme editor was just a matter of seeing how much joy it brought to our internal designers. We couldn’t keep that from our customers.”

Looking Ahead

Microsoft’s roadmap for Visual Studio 2026 includes a number of further Copilot integration points—natural-language debugging, automated PR descriptions, and a “/explain” command that generates architecture diagrams. The Copilot Usage window will eventually display those features as separate line items, allowing a fine-grained cost breakdown. The Theme Color Editor is expected to gain a “share” button that publishes a color scheme to the Visual Studio Marketplace, and toolset discovery will be extended to support the Windows Driver Kit and the Xbox GDK in future updates.

In the meantime, developers can try the new features by downloading the latest preview from visualstudio.microsoft.com. As always, Microsoft asks that bugs and suggestions be filed through the in-IDE Report a Problem tool or on the Developer Community portal.