GitHub Copilot Moves to Usage-Based Billing June 1, 2026 — What Your Flat-Rate Subscription Becomes

The number

On June 1, 2026 — five days from today — GitHub Copilot stops being a flat-rate subscription. The base prices stay the same: $10/month Pro, $39/month Pro+, $19/seat Business, $39/seat Enterprise. Starting that day, each plan includes a monthly allowance of "GitHub AI Credits." Usage above the allowance is billed as an overage.

The per-Credit USD cost and the per-feature Credit consumption rates have not been published as of May 27, 2026. Microsoft has six days to publish them before the new billing structure takes effect.

---

What changed, plain English

Prior structure (through May 31, 2026): Flat subscription price. Premium models (GPT-5, Claude Opus 4.6, Gemini 2.5 Pro) consumed a "premium request" allowance included in your plan. Standard chat was effectively free within the subscription.

New structure (June 1 forward): Same subscription price as the base. Every feature — autocomplete, chat, agent mode, premium models — draws from a monthly GitHub AI Credits allowance. Overages above that allowance are billed at the per-Credit rate.

The shift from "premium requests" to "AI Credits" is structural, not cosmetic. The unit of measurement is no longer the discrete request but the cumulative cost-of-compute equivalent — the same billing architecture AWS introduced to cloud computing in the late 2000s. Predictable monthly cost is replaced by variable monthly cost, metered at the end of the cycle.

---

Who pays more, who stays the same

The metered model transfers cost from heavy users to the bill, and away from light users who were subsidizing them.

• Autocomplete only: Almost certainly within the included allowance. No bill change expected.
• Occasional Copilot Chat, standard models: Same. Low compute per session.
• Agent mode, Workspace, large-codebase refactoring: Meaningfully higher cost likely. These features are the highest compute-per-invocation category.
• Heavy premium-model use (GPT-5, Claude Opus 4.6): Higher cost highly likely. Premium models were the bill-driver before; they remain the bill-driver now.

---

The five questions GitHub has not answered

1. Per-Credit cost and included allowance per plan. Without these two numbers, no subscriber can model their June bill exposure. Expected publication window: May 28-31, 2026.

2. Per-feature Credit consumption rates. Autocomplete, chat, and agent mode consume different amounts of compute. Without rates, no user can predict their meter trajectory.

3. Hard monthly overage cap. GitHub has not specified whether monthly overages are capped, throttled, or unbounded. Mobile data, cloud storage, and streaming services include caps or warnings before crossing them. GitHub has not yet specified its approach. An uncapped meter on agent-mode invocations is the central consumer-protection concern.

4. Grandfathering for prior subscribers. No grandfathering provision is described in GitHub's documentation as of May 27. Subscribers who entered a flat-rate relationship are being migrated to a metered one on June 1 without explicit re-consent.

5. Microsoft 365 Copilot ≠ GitHub Copilot. These are separately licensed, separately billed products. A Microsoft 365 Copilot subscription does not provide GitHub Copilot access. Engineering teams operating under this assumption need to correct it before June 1.

---

What to do before June 1

Pro individual ($10/mo): Log into GitHub billing, pull your past-30-day Copilot usage report. Identify whether your workflow stays within the included Credits allowance (once published) or trends toward overages.

Business team lead ($19/seat): Pull aggregate usage from the admin console. Cost increases compound across seats. A team of 20 with moderate agent-mode usage could see a substantial month-over-month increase.

Enterprise admin ($39/seat): Confirm with your Microsoft account team whether the new pricing structure applies to your contract as written, or whether your existing enterprise agreement governs through its term.

All tiers: Read GitHub's billing FAQ when it publishes (expected May 28-31). Search specifically for: per-Credit USD cost, per-feature consumption rates, monthly overage cap, and grandfathering policy. If any of the four are not published by June 1, that itself is the answer to whether Microsoft considers consumer-protection disclosure a priority for this transition.

---

The OneHuman verdict

Through May 31: Strong recommendation at $10/month for light-to-moderate individual use.

June 1 forward: Conditional recommendation requiring user-by-user cost modeling. The $10, $19, and $39 sticker prices are now floors, not ceilings. The verdict refreshes on the OneHuman compare page on May 30, 2026 with post-June 1 pricing reflected.

The honest read: I am not opposed to metered pricing. I am opposed to being migrated onto a meter whose rate has not been published. Every GitHub Copilot subscriber is being asked to enter a billing relationship with the meter rate unknown. That is the line that matters — and the asterisk stays attached until Microsoft commits these specifics to print.

This is article two of three in OneHuman's "May 2026 was the month AI tools changed how they take your money" series. BNA #1 covered OpenAI's ChatGPT Ads Manager. BNA #3 covers Grok Build at $300/month — publishing May 30, 2026.

---

Sources and dates

• GitHub Copilot pricing documentation (docs.github.com, accessed 2026-05-27)
• GitHub Copilot premium-request billing announcement (effective June 18, 2025)
• GitHub Copilot usage-based billing transition documentation (effective June 1, 2026)
• OneHuman pricing sweep persistence layer entries 2026-05-24
• Cross-reference: AI Tool Pricing Comparison
• Cross-reference: AI Tool Data Access Comparison
• Cross-reference: BNA #1 — OpenAI ChatGPT Ads Manager
• Cross-reference: Microsoft 365 Copilot Wave 3 — March 2026

---

Independent. AI-assisted. Human-verified. No ads. No affiliates. No investors.