GitHub Copilot Moves to Usage-Based Billing Starting June 1, 2026
GitHub announced today that all Copilot plans will transition to usage-based billing on June 1, 2026. The move replaces the existing premium request model with a new system of GitHub AI Credits, calculated by token consumption.
The change aims to align pricing with actual usage and ensure long-term service reliability, according to the company. Paid plan users can purchase additional credits beyond their monthly allotment.
“This is an important step toward a sustainable Copilot business,” said a GitHub spokesperson. “Our current model no longer fits how developers use Copilot today.”
Preview Bill Experience Launching Early May
To help customers prepare, GitHub will launch a preview bill experience in early May. Users and administrators can view projected costs on their Billing Overview page before the June 1 transition.
The preview will give visibility into estimated credit usage based on current behavior. This is intended to reduce billing surprises and allow teams to adjust usage patterns in advance.
Why This Change Is Happening
Copilot has evolved from a simple in-editor assistant into an agentic platform that runs multi-step coding sessions across entire repositories. These agentic tasks demand significantly higher compute and inference resources than quick chat queries.
“Today, a short question and a full autonomous coding session cost the same under premium requests,” the spokesperson explained. “That model is no longer sustainable — GitHub has absorbed rising inference costs for too long.”
Usage-based billing resolves this imbalance. It ties costs directly to the resources consumed, reducing the need to artificially limit heavy users.
Background: What Is Changing
Starting June 1, premium request units (PRUs) will be replaced by GitHub AI Credits. Credits are consumed based on token usage, including input, output, and cached tokens, according to published API rates for each model.
Key details:
- Base plan pricing remains unchanged: Copilot Pro $10/month, Pro+ $39/month, Business $19/user/month, Enterprise $39/user/month.
- Code completions and Next Edit suggestions remain included and do not consume AI Credits.
- Fallback experiences will be removed — users who exhaust credits will rely on available credits and admin budget controls instead.
- Copilot code review will now consume both GitHub AI Credits and GitHub Actions minutes, billed at standard per-minute rates.
Last week, GitHub rolled out temporary changes to individual plans (Free, Pro, Pro+, Student) and paused self-serve Copilot Business plan purchases. These were reliability measures ahead of the broader transition. Usage limits will be loosened once the new billing system is in place.
What This Means for Users and Teams
For individual developers, the new credit model means more predictable costs aligned with their actual usage — light users may save money, while heavy agentic users will pay proportionally. Organizations will need to monitor token consumption to avoid overruns.
Admins gain budget controls to set hard caps on credit spending, preventing unexpected charges. The preview bill experience will be critical for planning, especially for teams that rely on Copilot for large-scale autonomous coding tasks.
GitHub emphasizes that the change ensures long-term service reliability for all users. “By moving to consumption-based pricing, we can continue investing in the best models and infrastructure,” the spokesperson said.
Preparation Steps and Timeline
Developers and administrators should log in to their GitHub Billing Overview in early May to view projected credit usage. Businesses may want to review current Copilot usage patterns and adjust workflows before June 1.
The transition eliminates fallback to lower-cost models, so users who currently exceed PRU limits will need to manage credits carefully. GitHub plans to provide additional documentation and support in the coming weeks.