GitHub Copilot switched to token-based billing. Here is how to stay in control of the cost.

2026-06-02 · ~7 min read · Conor Dobbs

On June 1, 2026, GitHub Copilot moved to usage-based billing, and the developer forums lit up the same day. The threads I keep seeing have the same shape: a team turns on Copilot's agent mode, runs it the way they always have, and then watches the invoice land at several times what they expected. One r/cscareerquestions thread titled "Coworkers panicking over copilot billing" hit hundreds of upvotes within hours. Another captured the whiplash perfectly: corporate first said it "highly encourages" AI use, and now that the meter is running, the message has quietly become "be mindful."

The panic is real, but it is also avoidable. The change is not a price gouge so much as a shift in what you pay for, and that shift rewards people who understand where their tokens go and punishes people who do not. Here is what actually changed and what to do about it.

What actually changed

Copilot used to bill on a fixed monthly seat plus a count of "premium requests." As of June 1, every plan now includes a monthly allotment of GitHub AI Credits, and usage is metered against that allotment. The base seat prices did not move much: Copilot Pro is still $10/month, Pro+ is $39, Business is $19 per user, and Enterprise is $39 per user. The exchange rate is simple to the point of being blunt: 1 AI Credit equals $0.01, so a $10 monthly budget buys you 1,000 credits.

The important part is how credits get spent. Usage is calculated on token consumption — input, output, and cached tokens — at each model's published API rate. You draw down credits when you chat with Copilot, run agents, or use Copilot CLI, Spaces, and Spark. When you exhaust your allotment, you either stop or pay overage to keep going.

Two details matter more than the headline. First, plain code completions and Next Edit suggestions are still included and do not consume credits. The autocomplete most people think of as "Copilot" is largely unaffected. Second, the cheap fallback model that used to absorb spillover has been removed, so heavy work now lands on full-rate models. That single change is most of why power users running agentic sessions are projecting cost increases in the 10x to 50x range, according to early coverage of the backlash.

Why agents get hit the hardest

If your bill barely moved, you are probably using Copilot as autocomplete, and you can mostly stop reading. If your bill exploded, you are almost certainly running agent mode, and the reason is structural, not a billing bug.

An agent runs in a loop. Every turn it re-sends the system prompt, the project context, the conversation so far, and a growing pile of tool outputs, then asks the model for the next step. A single "fix this failing test" task can quietly become dozens of round trips, each one re-reading a large context window. You are no longer paying per keystroke of suggestion. You are paying per token of everything the agent reads and writes on every step of a loop you cannot see.

This is the same dynamic I wrote about in how to cut your Claude Code bill: the spend on any agent is governed by how much it writes and how often the loop re-reads the same context, not by the sticker price per token. Token-based billing simply makes that dynamic show up directly on the invoice instead of hiding it inside a flat fee. The flat fee was subsidizing your heaviest sessions. Now it does not.

The real trap: you cannot manage what you cannot see

The thing that turns this into a panic is not the price. It is the blindness. Most developers have never looked at a token-level breakdown of their own usage, because they never had to. A flat subscription meant a $10 light month and a $10 heavy month cost the same. Now the heavy month is metered, and the first time most people learn what "heavy" costs is when the overage charge arrives.

The fix starts with visibility. Before you cancel the agent, throttle the team, or argue with finance, you need to answer three questions:

Which sessions actually burn the credits? It is rarely uniform. A handful of long agent runs usually dominate the bill while routine autocomplete is nearly free.
How many tokens are cached versus fresh? Most providers, including the models behind Copilot, price cached input far below fresh input. If your cache hit rate is low, every loop re-pays full freight for context it already sent.
Where is the loop re-reading the same context? Agents that rebuild their prompt from scratch each turn, or splice fresh data into the middle of the context, shatter the cache and multiply the cost of every step.

None of those questions are answerable from a monthly invoice total. They need a token-level view, which is exactly the gap this billing change exposes for the first time.

What to actually do

Separate completions from agents. Code completions and Next Edit are still free. If your developers mostly want autocomplete, the new billing barely touches them. Reserve agent mode for tasks that genuinely justify a multi-step loop, and make that a conscious choice rather than the default button.

Measure before you cut. Pull your token usage and find the few sessions that dominate. The instinct under bill shock is to ban the tool. The better move is to find the 10% of usage driving 90% of the cost and fix or scope just that. I worked through which agent is even worth running at all in Cursor vs Claude Code vs Aider; the leaderboard is not the lived experience, and the cheapest tool is the one that finishes your task in the fewest loops.

Stabilize your context. If you control how the agent builds its prompt, keep the order fixed, append rather than insert, and strip volatile values like timestamps out of the cached region. I went deep on why this is the single biggest lever in prefix-cache stability for coding agents. A high cache hit rate can cut input cost several-fold, and it works on any provider that discounts cached tokens, not just one.

Set a budget and watch it. Treat AI Credits like any other metered cloud spend: put a ceiling on it, alert before you hit it, and review where it went. The teams that will be fine in three months are not the ones who use Copilot the least. They are the ones who know, to the dollar, what their usage costs.

The honest bottom line

Usage-based billing is not inherently worse than a flat fee. For light users it is often cheaper, and for everyone it is more honest: you finally see what your AI tooling actually costs to run. The pain is concentrated on heavy agentic users who were quietly subsidized by the old model and never had to look at a token breakdown. The panic in those forum threads is the sound of that subsidy ending.

The durable response is not to fear the meter. It is to read it. Find your expensive sessions, raise your cache hit rate, keep completions free, and put a budget around the rest. Do that and the new billing becomes a dashboard instead of a surprise. The cheapest token, as always, is the one you did not need to re-send.