GitHub Copilot Shifts to Usage-Based Billing, Adds Budget Controls

TL;DR

• GitHub Copilot now uses usage-based billing with AI Credits for all plans as of June 1
• Copilot code review now consumes GitHub Actions minutes in addition to AI Credits
• New user-level budget controls let org admins set spending limits per user; Copilot Max tier now available for power users

What Dropped

GitHub flipped the switch on usage-based billing for Copilot. Every plan—Student, Pro, Pro+, and the new Max tier—now charges based on AI Credits consumed rather than flat monthly fees. Each plan includes a monthly allotment; go over it and you pay per credit at month's end.

The Dev Angle

If you're on an individual plan, you get a monthly credit allowance. Burn through it and GitHub will let you spend more (with some limits based on your account history). Organizations and enterprises get tighter controls: admins can now set per-user budgets, get notified when users approach limits, and adjust on the fly.

Copilot code review is now a dual-cost feature—it consumes both AI Credits and GitHub Actions minutes. Org admins can set a default runner at the organization level instead of configuring each repo individually, which saves setup time but means you need to factor Actions minutes into your Copilot spend planning.

The new Copilot Max tier targets power users with higher included usage and higher spending caps. Existing Student, Pro, and Pro+ subscribers can upgrade today; new sign-ups open in the coming weeks (new user registrations are currently paused across all tiers).

Should You Care?

If you're an individual on a free or Student plan: You now have a clear monthly credit budget. If you stay within it, nothing changes. If you exceed it, you'll be billed for overages—but GitHub may cap how much you can spend based on your account age and verification status. The recommendation: upgrade to the next tier if you consistently hit limits.

If you're on Pro or Pro+: Your plan now includes a specific monthly AI Credit allotment instead of unlimited access. Check the usage-based billing docs to see what's included in your tier. If you need more, Copilot Max is available as an upgrade.

If you're an org or enterprise admin: This is the big one. User-level budgets give you granular spend control—set a universal cap or override for specific teams. You'll get email alerts when users approach their limits. For Copilot code review, configure a default runner at the org level to avoid per-repo setup. Plan for Actions minutes as part of your Copilot budget.

If you're a power user: Copilot Max is built for you. Higher included credits and higher spending limits mean fewer surprises. Existing subscribers can upgrade now.

The honest take: this is a shift from unlimited-access pricing to metered consumption. If your team uses Copilot heavily, you'll need to monitor spend and set budgets. For light users, the monthly allotment probably covers you. The real question is whether your org's usage patterns fit the new credit model—check the docs and run the math before committing to Max.

Source: GitHub Changelog