Starting June 1, 2026, GitHub Copilot will move from a premium-request model to a usage-based billing system. Instead of counting requests, every plan will include a monthly allotment of GitHub AI Credits, which are consumed based on token usage — input, output, and cached tokens. This change ensures pricing aligns more closely with actual resource consumption, making the service more sustainable. Here are the key questions and answers to help you understand what’s happening and how to prepare.

Why is GitHub switching to usage-based billing for Copilot?

GitHub Copilot has evolved from a simple in-editor assistant into an agentic platform that can run long, multi-step coding sessions and use the latest models across entire repositories. These advanced capabilities demand significantly higher compute and inference costs. Under the old premium-request model, a quick chat and a multi-hour autonomous session cost the same, forcing GitHub to absorb escalating expenses. Usage-based billing fixes this imbalance by tying cost to actual token consumption. This approach better aligns pricing with usage, ensures long-term service reliability, and reduces the need to impose hard caps on heavy users. It’s a necessary step for a sustainable Copilot business.

What replaces premium request units (PRUs)?

On June 1, 2026, premium request units (PRUs) will be replaced by GitHub AI Credits. These credits are consumed based on token usage — including input, output, and cached tokens — at the published API rates for each model. The number of credits you get each month depends on your plan (Pro, Pro+, Business, Enterprise). If you need more, paid plans can purchase additional credits. Importantly, code completions and Next Edit suggestions remain free and do not consume any credits. This shift makes billing more transparent and directly linked to the resources you actually use.

Will my monthly plan price change?

No. Base plan pricing remains unchanged: Copilot Pro stays at $10/month, Pro+ at $39/month, Business at $19/user/month, and Enterprise at $39/user/month. What does change is how additional usage is billed. Instead of counting requests, you’ll receive an allotment of GitHub AI Credits each month. If you exceed that allotment, you can purchase extra credits. Code completions and Next Edit suggestions are still included in all plans at no extra cost. The only feature that gets affected is the fallback experience — which will no longer exist.

What happens to the fallback experience when I run out of credits?

Currently, if you exhaust your premium request units, Copilot automatically falls back to a lower-cost model, letting you continue working with reduced capabilities. Under the new system, this fallback will be removed. Instead, usage will be governed by your available GitHub AI Credits and any budget controls set by your admin. Once you run out of credits, you won’t be able to use agentic or advanced features until you purchase more or wait for the next monthly cycle. This change ensures that heavy usage is properly accounted for and helps maintain service reliability for everyone.

Does Copilot code review cost anything extra?

Yes. In addition to consuming GitHub AI Credits based on token usage, Copilot code review will also consume GitHub Actions minutes. These minutes are billed at the same per-minute rates as other GitHub Actions workflows. So when you run a code review that uses Copilot, you’ll incur costs from both the AI Credits (for the model inference) and the Actions minutes (for the compute environment). This is a change from today’s model, and it’s important to factor both into your budget planning.

How can I see my projected costs before the transition?

GitHub is launching a preview bill experience in early May 2026. This tool will give users and admins visibility into projected costs based on current usage patterns. You can access it from your Billing Overview page when logged into github.com. The preview shows estimated credit consumption and associated costs, helping you understand how the new model will affect your monthly bill before the June 1 transition. We strongly recommend checking this preview to adjust your usage or budget controls in advance.

What steps should I take to prepare for usage-based billing?

First, review the preview bill experience in early May to understand your projected credit consumption. Second, monitor your current usage patterns — especially long agentic sessions and code reviews — to see where your tokens are being spent. Third, if you’re an admin, set budget controls and spending limits in your organization settings. Fourth, remember that code completions remain free, so basic assistance won’t be affected. Finally, consider whether your plan’s included monthly credits are sufficient or if you need to budget for extra credits. This transition rewards efficient usage and provides a predictable cost model for all teams.