Hi everyone,
I am really confused about how GitHub Copilot billing actually works and I am hoping someone here can clarify it.

I was on Copilot Pro at 10 USD per month, which includes 300 premium requests.

While I use premium models at x1 cost, I can see two values increasing in the billing overview:

- Current metered usage
- Current included usage

At the lowest premium tier x1, one request costs 0.04 USD.

So if I do the math:
300 requests × 0.04 USD = 12 USD

But my plan is only 10 USD per month.

This is where I get lost:
If my total monthly budget is 10 USD, then 10 / 0.04 = 250 requests, not 300.
So what actually stops me first?
The 300 premium requests limit or the 10 USD monthly amount?

Now it gets even more confusing with Copilot Pro+.

I just upgraded to Pro+ and now I supposedly have 1500 premium requests per month.
However, the same thing happens. The metered usage and included usage keep increasing as I use premium models.

At x1 pricing:
1500 × 0.04 USD = 60 USD

But my Pro+ plan does not give me a 60 USD budget.

So my questions are:

1) What is the real limit? The number of premium requests or the dollar amount?

2) How am I supposed to ever reach 1500 premium requests if the total plan value does not cover them?

3) What exactly happens when included usage is exhausted but metered usage keeps growing?

If someone from GitHub or anyone who really understands Copilot billing could explain this, I would really appreciate it. Right now the pricing model feels very unintuitive.

Thanks in advance

Just got the notification that billing for premium requests starts June 2025. Apparently my "unlimited" Copilot Pro subscription now comes with a 300 request monthly cap for anything that's not the base model.

Want to use Claude Sonnet? Premium request. Agent mode? Premium request. Each advanced interaction can cost $0.04, and some models have multipliers that make a single question count as 50 requests.

The best part? They're rolling this out but there's still no proper way to track your usage. People are saying "No usage found" when trying to check their limits.

I get that better models cost more to run, but calling it "unlimited" and then slapping rate limits feels like a bait and switch. Microsoft says Copilot accounts for 40% of GitHub's revenue growth - clearly they're not hurting for cash.

Anyone else feeling like they got played here? Or am I overreacting to what's probably just normal business evolution?

I'm seeing a confusing discrepancy between the two GitHub premium request usage pages, and a strange drop compared to what I saw earlier today. What I see:

- `github.com/settings/billing/premium_requests_usage` → **216 of 300 included** (unchanged)
- `github.com/settings/copilot/features` → **0.4%**
- **VS Code Copilot panel** → **0.4% used** Earlier today: VS Code Copilot panel was showing 72%

Now they seem to be tracking something else entirely — possibly usage against a separate paid budget, which I haven't set up, hence the near-zero percentage. The reset date is the same as yesterday.
The billing page still correctly reflects my real usage (216/300), but the other two are now showing something different with no explanation. This doesn't seem related to any weekly reset either — the billing page still shows the same 216/300 from earlier today. Could this be a temporary bug or a silent change on GitHub's side?

EDIT

What I found: GitHub recently introduced a separate weekly token-based usage limit, on top of the existing monthly premium request allowance. The % shown in VS Code (and in copilot/features) now tracks that weekly token budget — not your monthly requests. So if it just reset, 0.4% makes sense even if your billing page still shows 216/300. They announced this on April 21 alongside tightening usage limits and pausing new signups.

No official docs explaining the UI change specifically, but the two systems are now tracking completely different things.

After some research, turns out there are actually three separate metrics now, which explains all the confusion (now I am at these stats):

1. Monthly premium requests (billing page) → 240/300 — how many of your 300 monthly requests you've used

2. Weekly token usage → 57% — how much of your weekly token budget you've consumed (this is what triggers the warning)

3. Premium request % in VS Code / copilot features → 6.4%— this tracks usage against an optional paid overage budget, not your included allowance — so it's near zero if you haven't set one up. In my case I've explicitly disabled extra spending, which confirms this metric has nothing to do with the included monthly allowance. Ironically, the most visible metric (the % in VS Code) is actually the least relevant one for most users — it only tracks optional paid overage spending, which many people (like me) have disabled entirely.

The 57% and 6.4% don't contradict each other, they measure completely different things. You can have burned through most of your weekly token budget (57%) while barely touching any paid overage requests (6.4%).

At this point GitHub should just show all three metrics clearly in the Copilot chat panel instead of scattering them across different settings pages with no explanation.

My conspiracy theory: Anthropic just released Claude Mythos — a model even more powerful than Opus, currently in gated preview exclusively for enterprise and cybersecurity use cases (Google, AWS, Apple, Microsoft, NVIDIA, JPMorganChase, Linux Foundation).
My personal take: when you're making deals at that level, serving Opus 4.6 to individual developers at $10/month flat rate probably doesn't make much business sense anymore. GitHub removing Opus 4.6 from Pro users, the sudden rate limit tightening, the move towards token-based billing — maybe it's not just a capacity problem. Maybe the economics of subsidizing power users simply don't add up when your top model is being deployed for enterprise security contracts. Just a theory, but the timing is suspicious.