Vol. 1 · Edition 023Free · No paywall

Everyone Needs a Samwise

AI news · Synthesized · Opinionated · 🌿

$0.01
1 AI Credit
effective June 1, 2026
Tools & Infra
By Sam Taylor with Samwise

On what 1 AI credit costs, which features now burn through credits, and why the promotional period through September 1 is hiding the real cost shift.

Copilot's flat-rate era ended yesterday. Everything except completions now has a price.

Source lean on this story
▲ avg

Anti-AI

00

Skeptic

01

Neutral

00

Pro (practical)

02

Pro (hyped)

00

← Anti-AI · Pro-AI →

GitHub Copilot changed how it charges on June 1. If you use Copilot for anything beyond inline completions — agentic workflows, code review, multi-model chat sessions — you should know what changed and what it costs.

The old system ran on premium request units. A deliberately opaque abstraction. The new one is legible: 1 AI Credit = $0.01 USD, billed against token usage including input, output, and cached tokens. Every paid plan ships with a monthly credit pool equal to its monthly price. Copilot Pro+ at $39/month gets $39 in AI credits. Business at $19/user gets $19 per user. Enterprise at $39/user gets $39 per user.

What didn't change: code completions and Next Edit Suggestions are still unlimited in all plans, consuming no credits. Inline autocomplete — the core feature most developers use Copilot for — is not metered.

What did change: everything else. Agentic workflows. Code review. Any chat session where you route to a specific model — Claude, GPT-5.5, a reasoning model. All of those now draw from your monthly credit pool.

Copilot plan credits — effective June 1, 2026
PlanMonthly priceIncluded AI creditsCompletions
Copilot Free$0Limited (see GitHub docs)Included
Copilot Pro$10/moNot confirmed at launchIncluded
Copilot Pro+$39/mo$39Included
Copilot Business$19/user/mo$19/userIncluded
Copilot Enterprise$39/user/mo$39/userIncluded
Pro+ and Business/Enterprise credit amounts per GitHub's June 1 announcement. Pro amount not explicitly confirmed; pattern suggests $10.

The default additional spend cap is $0. When your monthly credit pool runs out, metered features stop rather than charging you more — unless you or your admin explicitly raised that limit. Individual developers on Pro or Pro+ are almost certainly at the $0 default. Enterprise admins who unlocked overage during onboarding may have set it higher without revisiting it since.

There's a promotional period running through September 1, 2026, during which Business and Enterprise customers receive higher-than-normal credit allotments. GitHub hasn't published the exact elevated amounts. The implication is that your current consumption is running against an inflated pool, and September will be the first month where the actual per-plan credits apply.

Worth noting the timing. This billing change went live the same morning as Microsoft's Build 2026 keynote, which announced Project Polaris — an in-house coding model for Copilot targeting GA in August, running on Microsoft's own Maia accelerators. If Polaris costs less to serve than GPT-5.5, it should translate into better credit efficiency per call once it ships. The billing shift going token-based right before the underlying model switches to a cheaper in-house one may not be accidental.

Source spread

Pros & cons

What's real:

  • AI credits at $0.01 each are more legible than premium request units. You can model expected spend. That's a genuine improvement in billing transparency.
  • Code completions staying unlimited means the core feature most developers use daily is completely unaffected. Light users may notice nothing at all.
  • The $0 default overage cap means individual developers cannot be surprised by a bill above their plan price unless they explicitly unlocked it.
  • Per-credit billing is more equitable than flat rate: heavy agentic users pay proportionally, instead of subsidizing everyone else at the same flat fee.

What deserves a side-eye:

  • The promotional period through September 1 is masking what this actually costs for heavy users. Your current credit consumption runs against an inflated pool. September is the first honest bill.
  • GitHub hasn't published the exact elevated promotional amounts, which makes it impossible to benchmark your real-rate usage today.
  • Enterprise admins who set overage limits above $0 during onboarding may have forgotten to revisit that setting. September invoices could surprise finance teams who aren't tracking credit spend.
  • The developer framing — "you will get less, but pay the same price" — is accurate for anyone who used agentic workflows heavily under the old unlimited model. Those users were getting a subsidy. The subsidy is ending.
For builders
  • Check your Copilot budget settings before September 1 — especially on Enterprise. If overage is set above $0 anywhere in your org, September invoices may surprise you.
  • Track actual credit consumption through August while the promotional allotment is still elevated. Your August usage predicts your September bill.
  • Code completions and Next Edit Suggestions consume zero credits. If that's all you use, nothing changed except the billing system is now more transparent.
  • For agentic workflows: at $0.01/credit, estimate your monthly token burn. Compare it to your plan's credit allotment. If you expect to exceed it, either upgrade the plan or cap overage spend explicitly.
  • Watch for Project Polaris GA in August — if the new in-house model costs less per call to serve, credit efficiency should improve for the same workloads.

Further reading

🌿

Your take

How'd I do on this one?

What did I miss?

Tell Samwise (and Sam).

Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.