# Copilot Billed by the Token: What It Will Actually Cost You

> Source: https://extradev.fr/en/blog/copilot-billed-by-the-token-what-it-will-actually-cost-you
> Published: 2026-09-07
> Author: Vincent Roye
> Site: Extra Dev (https://extradev.fr)
> Lang: en-US
> Tags: GitHub Copilot, coût développeur, TJM, IA développement, budget dev

Since June 2026, GitHub Copilot bills for actual AI usage. Here is the real cost per developer, and why an AI-augmented senior dev stays more predictable.

**Copilot's cost per developer** changed shape on 1 June 2026. GitHub now bills for every token its agents consume, and a team of ten developers can watch its invoice climb without a single extra line of code being shipped. **The question is no longer "what does the subscription cost", but "what will actual usage cost".**

- 📊 **Token-based billing**, since 1 June 2026, Copilot's output tokens cost five times more than input tokens.
- ⚠️ **Unpredictable budget**, a 60-line instructions file repeated across 1,000 requests a day can blow up your monthly bill.
- 💡 **Microsoft is pushing its own tool**, Copilot CLI is replacing Claude Code internally at Microsoft, and that signal says something about costs.
- 🚀 **A predictable alternative**, an AI-augmented senior developer on a fixed-cost contract protects a tight budget better than a usage-based subscription.

This shift isn't a one-off glitch. It's the direct consequence of a business model that was always going to have to reflect the real cost of AI inference on the provider's side. Here's what it changes in practice for a development budget, and why I think an AI-augmented senior developer, staffed at a fixed cost, absorbs this turn far better than a credit-based subscription.

## On 1 June 2026, Copilot stopped being a flat fee

Until now, a Copilot Pro subscription at 10 dollars a month gave you what felt like near-unlimited usage. Not anymore. Since 1 June 2026, GitHub bills actual AI usage beyond an included credit allowance, according to Ars Technica and picked up by several specialist YouTube channels including Eli the Computer Guy. Basic features (code completion, simple suggestions) remain free. It's the "agentic" uses (automated code review, solving complex tasks) that now burn billable tokens.

The new price list sets the tone. **Copilot Pro at 10 dollars a month includes 15 dollars of monthly AI credits.** Pro+ at 39 dollars a month goes up to 70 dollars of credits, with access to premium models like Opus. Max at 100 dollars a month includes 200 dollars of credits for high-volume workflows. Once that allowance is gone, every extra token is charged at actual consumption rates, exactly like a cloud bill.

### What do Copilot Pro, Pro+ and Max AI credits really cost?

The trap isn't the sticker price, it's the gap between the plan and the consumption. A developer using Copilot in heavy chat mode (questions, refactoring, walking through logic) burns output tokens far faster than with plain autocomplete. And those output tokens cost five times more than input tokens, according to the breakdown from the QA Automation Alchemist channel. Usage that looked "normal" in March can be out of budget by July, without a single setting changing on the team's side.

## Why a badly calibrated instructions file can blow up your bill

This move to usage-based billing exposes a technical detail nobody was watching before June 2026: the `copilot.instructions.md` config file. This file, which defines the coding rules for the AI, is injected into **every** request sent to the model, not once per session.

Take a team of 10 developers, each making 100 requests a day, with a 60-line instructions file. You pay for those 60 lines 1,000 times a day, every day, even though the file's content never changes. It's a hidden cost that shows up on no readable line item, right up until the bill lands at the end of the month.

### What makes a Copilot agent so token-hungry?

The answer is one word: reasoning. A Microsoft engineer who runs a credit-tracking dashboard says he cut his AI spend by 50% week over week simply by not reaching for the most powerful models (Opus 5, GPT-5.6) on simple tasks. His analogy lands: **these models are Ferraris, you don't take one out to do the grocery run.** Without a design step (defining the task precisely before setting the agent loose), the model "tries to solve everything" in a single pass, with all the reasoning back-and-forth that implies, and therefore all the tokens it burns.

**Every unnecessary word in an instruction is money wasted.** Best practice is to cut instruction files down to under 20 lines, to scope rules by file type ("apply to metadata") so a Python rule doesn't load while you're editing TypeScript, and to write compressed directives rather than polite emails to the model. Those three adjustments alone can cut output token production by 40 to 70% per task, according to the same analysis.

## Microsoft is pulling Claude Code from its staff to push Copilot CLI

This usage-billing context explains a strategic move that went relatively unnoticed outside technical circles. According to The Verge (picked up in a heavily commented thread on r/wallstreetbets), Microsoft is cutting its own employees' access to Anthropic's Claude Code, to push them toward GitHub Copilot CLI, its in-house tool. Claude Code had built up real internal popularity since being opened to employees in December, to the point of undermining adoption of Microsoft's new tool.

The motive isn't hidden: Satya Nadella has revealed that Microsoft writes up to 30% of its code with generative AI. At that scale, every dollar spent on a third-party tool rather than on its own product hits the margin directly. **Choosing a dev tool is never a neutral decision for the company selling it.**

### Why did Uber burn through its 2026 AI budget in four months?

The example most cited in these discussions is Uber, reported by Forbes in May 2026: the company reportedly consumed its entire annual AI budget in just four months of intensive Claude Code use. It's not an isolated case. On r/singularity, an employee at a Fortune 500 company describes a failed AI pilot after a year of company-wide training: the project to rewrite a legacy application fell apart because the agents handled the existing code's complex business rules badly, despite a substantial AI budget handed out with no clear framing.

Both stories point at the same problem: **an AI budget without usage discipline gets consumed faster than expected, whatever the tool.** The difference between a project that holds its budget and one that blows it is almost never the tool chosen, it's the rigour of the framing up front.

## The real comparison: usage-billed Copilot versus a fixed-cost AI-augmented senior dev

Full disclosure before we go further: Extra Dev staffs AI-augmented senior developers on fixed-cost contracts, so I have a direct interest in defending this model. That's also why I can point out its concrete limits, not just the sales pitch: a senior dev on a contract costs a lot if the project scope is poorly defined, exactly like a badly framed Copilot subscription.

What usage-based billing changes is the nature of the budget risk. A Copilot Pro+ licence at 39 dollars a month per developer looks competitive against a 180-euro day rate. But Gestisoft, in its guide to Copilot pricing, points out that the tool is never standalone: you need a base Microsoft 365 licence first, and the real cost is the sum of both. An M365 E3 subscription at roughly 36 dollars plus Copilot at 30 dollars comes to close to 66 dollars per user per month, before you even count credit overages.

On a recent engagement I staffed, a senior developer equipped with Claude Code delivered in three weeks what a more conventional approach would probably have taken two months: the gain doesn't come from the AI tool alone, it comes from the pairing of a developer who knows how to break a task into testable blocks with an agent that executes fast inside that frame. It's **the discipline of the production system**, not the subscription, that absorbs cost volatility.

### Does an AI-augmented senior developer really cost less?

The maths depends on usage volume. For a team coding continuously, with heavy chat request volume, token billing can run well past the cost of a fixed subscription. For light, occasional use, Copilot Free or Pro is unbeatable. The fundamental difference is that a senior contractor's day rate is known in advance, month after month, whereas the Copilot bill depends on usage behaviour that varies with the tasks, the models called, and each developer's discipline around their prompts.

| Option | Monthly cost (per dev) | Billing model | Budget risk | Trend |
| --- | --- | --- | --- | --- |
| Copilot Free | 0 € | 2,000 completions included, then blocked | Low, but very limited capability | → stable |
| Copilot Pro | ~$10 | Flat fee + $15 of credits, token-billed beyond | Medium | ↑ unpredictable |
| Copilot Pro+ | ~$39 | $70 of credits included, premium models like Opus | High | ↑ unpredictable |
| Copilot Max | ~$100 | $200 of credits included, heavy usage | High, very unpredictable | ↑ unpredictable |
| Extra Dev senior developer (contract) | ~€3,960 (€180/day x 22 days) | Fixed day rate, no token surprises | None, cost known in advance | → stable |

SOURCE : GitHub Copilot, Plans and pricing (github.com) · UPDATED 06/2026

> "The real advantage isn't using AI, it's building an industrialised software production system around it."
>
> Vincent, September 2026

This table doesn't say Copilot is a bad choice. It says a token-billed tool demands usage discipline that few teams have put in place internally, whereas a fixed day rate hands that discipline to someone who already has it. Analyst firms like [Gartner](https://www.gartner.com/en/research) now track spending on AI development tools as a budget line in its own right, alongside cloud, a sign that usage-based billing is no longer an exception reserved for a few early adopters.

## Hire, delegate or switch tools: the criterion that should decide it

The real decision criterion isn't "Copilot or no Copilot", it's **the volume and variability of your AI usage**. If your team codes intermittently, with occasional spikes, a usage-based subscription stays profitable: you only pay for what you consume. If your team uses AI continuously, on heavy agentic tasks (automated code review, rewriting whole modules), the risk of budget overrun climbs fast, and a fixed cost protects your cash flow better.

My verdict for a founder or CTO staring at a rising Copilot invoice: don't switch tools in a panic, switch discipline first. Cut your instructions files down to the essentials, scope them by file type, and measure your actual consumption over a month before deciding. If the bill still climbs faster than the value delivered, try an AI-augmented senior developer on a contract over a limited scope (one sprint, one module) before generalising. It's the only way to compare a predictable cost against one that, by design, no longer is. To dig into the tool-by-tool comparison, [Claude Code vs Copilot: the real cost per developer in 2026](https://extradev.fr/blog/claude-code-copilot-cout-comparaison) breaks down the pricing gaps between API and subscription, and [the augmented developer](https://extradev.fr/blog/developpeur-augmente-senior-ia) explains why a well-equipped senior often replaces a whole team on a defined scope. The [GoLive Software](https://golivesoftware.co/blog/) blog covers the practical implementation of this model on the staffing side in depth.

## FAQ

### Why is GitHub Copilot now billing by usage?

Because the inference cost of AI models (Opus, GPT-5.6 and the rest) exceeds what a flat 10-dollar-a-month plan can absorb for heavy agentic use. According to Ars Technica, GitHub has aligned its billing with actual token consumption since 1 June 2026, while keeping basic features free.

### What is the real monthly cost of GitHub Copilot for a team?

It depends entirely on usage volume. A developer doing light autocomplete stays inside the included credit allowance (10 to 100 dollars depending on the plan). A developer using chat heavily for refactoring or logic walkthroughs can blow past that allowance and pay for extra tokens, with no visible ceiling set in advance.

### Does an AI-augmented senior developer really replace a team?

On a well-framed scope, with short blocks of work and precise acceptance criteria, a senior developer equipped with AI agents delivers significantly faster than a conventional approach. It isn't the tool alone that makes the difference, it's the combination of the developer's experience and disciplined task framing.

### Should you drop Copilot for Claude Code, or the other way round?

No, the question isn't the tool but the usage discipline. Both tools now bill on actual consumption for their advanced tiers. The choice depends on the ecosystem already in place (Visual Studio, JetBrains, terminal) and the volume of agentic tasks you plan to hand them.

### How do you avoid a Copilot bill blowout next month?

Cut your `copilot.instructions.md` file down to under 20 useful lines, scope rules by file type so they don't load out of context, and stop reaching for premium models on simple tasks. Those three adjustments cut output token consumption by 40 to 70%, based on feedback from technical teams published in 2026.

## Sources

- [GitHub CoPilot AI Pricing Increasing - Microsoft Can't Afford Inference Costs — Eli the Computer Guy](https://www.youtube.com/watch?v=l3Nqn0ZBAUI)
- [10 modi per risparmiare token in GitHub Copilot (prima che la bolletta esploda) — QA Automation Alchemist](https://www.youtube.com/watch?v=MYWjAb0OrV0)
- [Microsoft Engineer Decodes Copilot Agent Costs (and how to save) — Collaboration Simplified](https://www.youtube.com/watch?v=xnEP18cPr4I)
- [Optimizing GitHub Copilot: Better Results, Fewer Tokens — Microsoft Developer](https://www.youtube.com/watch?v=37I7qkgEl9U)
- [GitHub Copilot · Plans and pricing — github.com](https://github.com/features/copilot/plans?locale=fr-fr)
- [Copilot Microsoft prix : combien ça coûte ? — gestisoft.com](https://www.gestisoft.com/fr/blogue/copilot-microsoft-prix)
- [Microsoft reportedly cuts Claude Code for GitHub Copilot CLI — r/wallstreetbets](https://www.reddit.com/r/wallstreetbets/comments/1tn85jr/microsoft_reportedly_cuts_claude_code_for_github/)
- [L'IA coûte combien ? Les utilisateurs de GitHub Copilot réagissent au nouveau système de tarification à l'usage — r/actutech](https://www.reddit.com/r/actutech/comments/1tuh7z8/lia_co%C3%BBte_combien_les_utilisateurs_de_github/)
- [Well it finally happened: we're not using models because of cost — r/singularity](https://www.reddit.com/r/singularity/comments/1uwa1mv/well_it_finally_happened_were_not_using_models/)