GitHub Copilot's Included Credits Drop on 1 September 2026: What It Costs Your Team
Promotional AI Credits end 31 August. Business falls from $30 to $19 of included usage per seat, Enterprise from $70 to $39 — same subscription price, 37-44% less included. What to check before the invoice.
DevTools Review
Get told when a price changes
We re-verify all 12 tools. You hear from us only when something actually moved.
Buying for a team? Price your team's bill on every plan, free. Takes under a minute.
If your organisation pays for Copilot Business or Enterprise, your September invoice can be larger than August’s without anyone changing anything. Here is exactly what changes and what to check.
What changes on 1 September
GitHub moved Copilot from premium request units to usage-based AI Credits on 1 June 2026, and gave organisations elevated included credits for the first three months. From GitHub’s announcement:
| Plan | Price/seat | June–Aug included | From 1 Sept | Change |
|---|---|---|---|---|
| Business | $19/mo | $30 in credits | $19 in credits | −37% |
| Enterprise | $39/mo | $70 in credits | $39 in credits | −44% |
| Pro | $10/mo | $10 | $10 | — |
| Pro+ | $39/mo | $39 | $39 | — |
The subscription price is unchanged. What changes is how much usage is included before you start consuming budget.
Individual Pro and Pro+ plans were not part of the promotion, so nothing changes for them on that date.
The part that stops people panicking
Code completions are not billed in credits. Inline suggestions and Next Edit Suggestions remain unlimited on every paid plan. Credits meter chat, agents, and premium model usage — the token-consuming interactions, priced against each model’s published rate.
So if your team mostly uses Copilot as autocomplete, this change may cost you nothing at all. If your team leans on agent mode and premium models, it is the difference between a flat invoice and a variable one.
That distinction is the whole question, and only your own usage data answers it.
What to actually do, before 1 September
1. Read your August usage. In your organisation’s Copilot billing view, find credits consumed per seat during August. That figure was measured against a $30 (Business) or $70 (Enterprise) allowance. Compare it to $19 or $39.
If a seat burned $24 of credits in August, it was comfortably inside the promotion and will be over the standard allowance in September.
2. Check your spend policy. GitHub states organisations “can choose whether to allow additional usage at published rates or cap spend.” That admin setting decides what happens at the ceiling: an overage bill, or agent features stopping for developers mid-sprint.
Neither is wrong. Both are bad to discover by accident. Decide deliberately and tell your team which one you chose.
3. Only then consider whether the plan still fits. If a meaningful share of seats will exceed the standard allowance every month, the honest comparison is your all-in per-seat cost against the alternatives — not the sticker price.
How the alternatives price
| Feature | G GitHub Copilot | C Cursor | C Claude Code | W Windsurf (Devin Desktop) |
|---|---|---|---|---|
| Price | $10/mo | $30/mo | $20/mo (via Pro) | $20/mo |
| Autocomplete | Very Good | Excellent | Good | |
| Chat | ||||
| Multi-file editing | ||||
| Codebase context | Workspace | Full project | Full project | Full project |
| Custom models | ||||
| VS Code compatible | ||||
| Terminal AI | ||||
| Free tier | ||||
| Try GitHub Copilot | Try Cursor Free | Try Claude Code | Try Devin Desktop Free |
At 50 seats, Copilot Business is $11,400/year before any overage. Cursor Teams at $40/seat is $24,000. That gap is wide enough that Copilot stays the cheaper option through a substantial amount of overage — which is worth calculating rather than assuming in either direction.
Try GitHub CopilotClaude Code at $20/month is the other shape worth pricing: it runs alongside any editor rather than replacing it, and is strongest at exactly the whole-task work that burns Copilot credits fastest. For a team where a few developers do most of the agent work, pairing a cheap seat for everyone with a stronger tool for those few can beat upgrading the whole organisation.
One source correction
Several third-party write-ups of this change describe overage as opt-out — that it happens automatically unless an admin prevents it. GitHub’s own wording is that organisations choose whether to allow additional usage or cap spend, which is a choice rather than a default.
We could not confirm the opt-out framing on GitHub’s own pages, so we are not repeating it. Check your own admin settings rather than trusting anyone’s description of the default, including ours.
Frequently asked questions
Verified against GitHub’s own billing announcement and plans page, August 2026. We earn nothing from any link on this page and are not enrolled in an affiliate programme for any tool here — full disclosure.
Need this modelled at your headcount before the invoice? Our $299 audit prices your actual credit burn against the alternatives and gives you a written recommendation for finance.
Make an AI coding tool? Developers read this page when they're about to pay for one. Sponsor it →
Written by the DevTools Review team
We research AI coding tools from vendor documentation, pricing pages, changelogs and public user reports, and re-check prices against vendors' own pages. We don't claim hands-on testing we haven't done. How we work.