GitHub Copilot individual plans: Introducing flex allotments in Pro and Pro+, and a new Max plan

We’ve heard your questions about whether the included usage in each GitHub Copilot plan will go far enough when we transition to usage-based billing on June 1st. Longer agent runs, multi-step work, and more capable models will all put pressure on the usage amounts detailed in our original announcement.

We’re updating the individual lineup based on that feedback. Pro and Pro+ will include more total usage at the same price through a new flex allotment, and we’re introducing Max, a new plan for sustained, high-volume Copilot work.

What’s included

The individual Copilot lineup will span  Free, Pro, Pro+, and Max, with usage-based billing across all plans. Free will continue to include a limited number of code completions each month, plus limited chat and agent usage with auto mode.

For paid plans, monthly included usage comes in two parts:

• Base credits: matched 1:1 with your subscription price. These never change. 
• Flex allotment: variable additional usage on top of your base. Flex allotments will vary over time.

Below are the individual plans as of June 1, 2026:

How it works

Your base credits are used first. If you go beyond your base, the flex allotment is applied automatically at the same rates across your IDE, github.com, and the CLI. You don’t need to turn anything on or manage a separate bucket; your dashboard will show what’s available and what you’ve used. And if you use everything included in your plan, you can purchase more usage and keep going.

Code completions and next edit suggestions remain unlimited on paid plans and don’t consume credits.

Why flex can change

The flex allotment is a variable part of your included usage; it is designed to adapt as the economics of AI evolve, including model pricing, new models, and improvements in efficiency. Your base credits, which are 1:1 to your subscription price, will always stay the same.

What to do

Nothing. If you’re on a monthly Pro or Pro+ plan, the additional usage lands automatically on June 1 when you migrate to usage-based billing.

Written by

Joe Binder

@binderjoe

VP of Product