GitHub Copilot shifts to usage-based billing in 2026

GitHub is changing how Copilot is billed. Starting June 1, 2026, all Copilot plans will move to usage-based billing, with usage measured through monthly GitHub AI Credits instead of the current premium request unit system.

The company said plan prices will stay the same, but the way customers consume included usage will change. In practice, that means Copilot customers will no longer be thinking in terms of a fixed bucket of premium requests. Instead, the service will track token consumption, the standard unit used by large language models to count text input and output.

GitHub announced the update in a company news post, saying the new billing model applies across Copilot plans. The change is aimed at tying cost more directly to how much AI work users actually do, rather than to a narrower request-based meter that can be harder to map to real model activity.

For people who use Copilot only as a coding assistant in an editor, the shift may not feel very different day to day. But for teams running larger workloads, especially those using Copilot more heavily across multiple users, the billing logic now looks more like other cloud AI services that charge based on consumption.

That matters because token-based billing is easier to align with model usage, but it can also be harder to predict if users are generating long prompts, larger code outputs, or multiple follow-up requests. GitHub is responding to that concern with new budget controls for organizations, which should give admins more visibility into how credits are being used.

GitHub AI Credits will become the monthly unit for included usage, replacing premium request units. The company has not changed the advertised plan prices, but customers will need to adapt to a new system for tracking what is covered and what counts against usage.

The move also reflects a broader shift in the AI software market. As more products build on large language models, vendors are moving away from flat-fee access to metered models that mirror backend compute costs. That is especially common when a service depends on third-party model APIs or on internal model infrastructure that is expensive to run at scale.

For GitHub, the timing is notable because Copilot has become one of the company’s most visible AI products and a key part of Microsoft’s developer tooling story. Any change to its billing model affects not just individual programmers, but also enterprises that have started standardizing on Copilot for internal development workflows.

GitHub said organizations will get new controls to manage budgets under the updated system. Those controls are likely to matter most for admins who need to keep AI spending predictable across departments, projects, or shared seats, especially as Copilot use expands beyond autocomplete into more agent-like and conversational workflows.

The company’s announcement leaves Copilot’s core pricing intact, but it replaces the old request-based accounting model with a consumption-based one that is tied to token usage and managed through monthly GitHub AI Credits.