GitHub Copilot: Usage Tracking and Alerts in Visual Studio
Visual Studio's Copilot Usage window has been refreshed to reflect usage-based billing with real-time consumption data and proactive alerts at three stages: approaching the monthly limit, hitting it, and entering overage. The change follows GitHub's June 1 switch of all Copilot plans to token-based billing, after which some developers running agentic sessions burned through a Pro plan's entire monthly credit allotment in a single sitting. The default warning threshold is 75% of the monthly limit, and it's adjustable in settings.
Sources & Mentions
3 external resources covering this update
InfoWorld β Visual Studio update rejiggers GitHub Copilot usage tracking
InfoWorld
TechTimes β Visual Studio 2026 Fixes Copilot Billing Blind Spot With Native Cost Tracker
TechTimes
DevOps.com β GitHub Copilot Bills Hit $800: Visual Studio's June Update Adds Real-Time Usage Alerts and MCP Trust Checks
DevOps.com
Closing a Billing Visibility Gap
When GitHub moved every Copilot plan to token-based, usage-based billing on June 1, 2026, it created a new problem: developers running long or complex agentic coding sessions had no reliable way to see how much of their monthly allotment a session was consuming until the bill arrived. Some Pro plan users reportedly exhausted their entire $15 monthly credit allowance in a single agentic run. Visual Studio's June update addresses that gap directly.
A Real-Time Usage Window
The refreshed Copilot Usage window, accessible from the Copilot badge menu, now shows consumption under the token-based billing model with real-time updates rather than a delayed or static snapshot. Developers can check in on how much of their monthly usage they've consumed at any point during a session, rather than discovering it after the fact.
Three-Stage Alerts
Proactive alerts now notify developers at three distinct points: when they're approaching their monthly limit, when they've hit it, and when overage billing activates beyond it. The default warning threshold is set at 75% of the monthly usage limit, but it can be tuned from Tools > Options > GitHub > Copilot > Copilot Chat, under "Quota warning threshold percentage," letting developers choose how much runway they want before the first warning appears.
Why It Matters
This is less a new capability than a necessary companion to Copilot's shift toward usage-based pricing. As agentic workflows consume variable and sometimes unpredictable amounts of usage per session, giving developers visibility into consumption in real time, rather than after a surprise bill, is central to making that pricing model workable in practice.