Starting June 1, 2026, GitHub Copilot code review will be billed as AI Credits under a new usage-based model, according to StartupFortune. This shift to usage-based billing replaces premium request units with GitHub AI Credits, altering how developers and organizations will be charged for AI assistance. One GitHub AI credit is valued at $0.01, per TechCrunch. This change has already spurred consternation among developers.

GitHub Copilot subscription prices appear stable on the surface. However, the introduction of AI Credits for features like code review shifts cost risk to users. This could lead to unexpected expenses for development teams.

Companies are likely to face increased and less predictable costs for AI-assisted development. This prompts a re-evaluation of their current tooling and budget allocations.

Who Pays More? The Impact on Teams and Budgets

  • For existing Copilot Business customers, the included allotment is 3,000 AI credits per user per month from June 1 to September 1, 2026, according to TechCrunch.
  • This allotment drops to 1,900 credits per user per month after September 1, 2026, effectively nearly halving the included credit allowance for businesses.
  • Copilot Business monthly seat pricing remains $19 per user per month, including $19 in monthly AI Credits, according to GitHub.
  • Copilot Pro monthly subscriptions include $10 in monthly AI Credits, and Copilot Pro+ monthly subscriptions include $39 in monthly AI Credits, according to GitHub.

While base subscription prices remain constant, the reduced credit allotment for Business customers post-September 2026 implies a potential hidden price increase for teams with consistent or high code review usage. This change forces businesses to purchase additional credits for the same usage after the grace period.

The Shift to Metered AI: Why Now?

GitHub Copilot code review consumes GitHub Actions minutes, charged for private repositories at standard Actions rates, according to TechCrunch. This cost is a separate line item from AI Credits, introducing a second, potentially hidden, usage-based cost.