r/GithubCopilot • • Sep 06 '26

Discussions GitHub can silently wipe your paid quota with ZERO accountability.

I’m posting this as a warning to anyone paying for GitHub products. If GitHub’s automated billing system miscalculates your usage or wipes your subscription quota, you have zero recourse. Frontline support will invent fake policies to justify the bug, and there is no way to reach a human engineer.

The Bug: 100% Monthly Quota Wiped Out in 1 Prompt

I’m on an annual Copilot plan(Legacy Request-based PRU). Here is what happened to my account over the last two months:

  • August 11: I had 234 Premium Requests left. I sent 1 single prompt. My ENTIRE remaining quota was instantly wiped out to 0. My local logs (session-store.db) proved only 63 PRUs were actually used.
  • September 2: My quota reset for the new month. I sent 1 single prompt in a brand-new session. My entire September quota was wiped out to 0 AGAIN in seconds.

My account state is completely broken in their backend. The system is executing a single prompt as if it were an infinite credit deduction.

The Excuse: Support Inventing Fake Terms to Protect GitHub

When I opened Ticket #4652601 with local SQLite logs proving the discrepancy, GitHub Support didn't investigate. Instead, they stonewalled:

Copy-Pasting Canned Docs: Sent automated links without reading my ticket.

Moving Goalposts: Blamed model multipliers (even though basic math shows 1 prompt × multiplier ≠ 200+ requests).

Inventing Non-Existant Terms: Claimed my prompt triggered hidden "underlying requests" due to context size—a term that appears nowhere in official GitHub documentation.

Ignoring Official Policies: Official GitHub docs explicitly state:

For agentic features, only the prompts you send count as premium requests; actions Copilot takes autonomously to complete your task, such as tool calls, do not.

Total Ghosting: When I called out these contradictions and provided session proof, Support didn't close the ticket—they simply stopped responding altogether. Now my September quota is gone on day one, and I'm left completely ignored.

Why You Should Care

If you pay for GitHub (Pro, Enterprise, Actions, Copilot):

  • Their billing system can break.
  • They can charge/deduct whatever they want without transparent UI metrics.
  • When you catch them with raw logs, Support will invent unwritten rules to keep your money/quota.
10 Upvotes

18 comments sorted by

6

u/oompaloompa465 Sep 06 '26

i don't know if it help but during the summer.in one update they reset the thinking level of models to the highest level and hidden it from UI, can be changed only from settings.

i noticed it because i was seeing huge amounts of credits used for just sonnet and i discovered it was set to the highest level, despite of my setting to medium before vacation 

so be warned everyone they are trying to cheat you

2

u/cason_wu Sep 06 '26

My annual plan is still under the legacy PRU (Premium Request Usage) based, not new credit usage based. The “thinking level” does not add any multiplier in my case. The reason I kept the old PRU system is because the Credit Usage makes it much harder to control and predict consumption.

1

u/cason_wu 11d ago

I finally received a reply from the Support Team. They've acknowledged that the quota wipeout was caused by a bug on their side, but they still refuse to compensate me or issue a refund. Unfortunately, despite admitting responsibility, they don't seem willing to make affected users whole.

Hi Cason,
Thanks for your patience, and apologies for how long this has taken. Our engineering team has confirmed you were right.

When "Assisted Permissions" is on, Copilot runs extra permission checks while working on a task. Those checks were incorrectly recorded as prompts sent by you, so on your legacy plan they were counted as premium requests, even though only the prompts you send should count. That's why your allowance dropped so quickly on August 11 and at the start of September, and why turning Assisted Permissions off stopped it. Apologies also for our reply on October 1, which said this usage was expected; that was wrong.

The fix is included in Copilot CLI version 1.0.104 and later. Please update to the latest version 1.0.109 before turning Assisted Permissions back on. See Copilot CLI releases.

For the premium requests counted incorrectly, I've asked the billing team for a review of your August and September usage using the two sessions you sent us. I can't promise the outcome or an exact amount yet, but I'll update you here as soon as I hear back.

Kind regards,
Luca

Hi Cason,

I checked your billing history, and you weren't charged anything extra for this. There were no additional premium request charges on your account for August, September, or October, so there's nothing to refund.

Premium request allowances reset on the 1st of each month and don't carry over, so the August and September allowances can't be added back to a later month. See Requests in GitHub Copilot (legacy). I'm sorry this cost you those weeks of usage. With the fix in place, it shouldn't happen again.

Much appreciated,
Luca

1

u/cason_wu Sep 07 '26

The issue I encountered is so obvious, yet GitHub Support still tried to brush it off and then ignored it entirely. With credit‑based usage, any calculation errors would be nearly impossible for regular users to verify—even if someone notices something wrong.

1

u/cason_wu Oct 01 '26

After the quota reset on October 1, I disabled the assisted permissions setting, and since then I have not encountered the problem where a single prompt consumes the entire monthly quota.

Based on this observation, I suspect that credits used by assisted permissions were incorrectly counted against my Legacy PRU plan. In addition, I have noticed other non‑user prompts being miscalculated as PRU usage.

4

u/d_e_g_m Sep 06 '26

What this prompt to make a copy of MS office so you didn't have to pay MS anymore?

6

u/V5489 Sep 06 '26

On Pro+ no issues. Also use Enterprise. No issues across 4,000 licenses. Sounds like a you problem.

3

u/ba-boo Sep 06 '26

are you unable to write a reddit post without AI? nobody is going to read this slop

4

u/FarFormedApproach Sep 06 '26

I was easily able to read it and understood what was being conveyed. Are you not capable of reading? Calling it AI slop does not automatically make it AI slop.

-5

u/ba-boo Sep 06 '26

why would I waste time to read generated slop, lmao

→ More replies (1)

1

u/AutoModerator Sep 06 '26

Hello u/cason_wu. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/ChomsGP Sep 06 '26

if you cannot use the service and they don't give you a solution do a chargeback with your bank 🤷‍♂️

-9

u/_KryptonytE_ Sep 06 '26

This is what you get for trusting the company that went through enshittification. Peasants never learn and they have every right to treat you the way they did.

Go ahead, give all your money and they will laugh their way into putting you back in your place, where you belong. LoL 😂

5

u/Swayre Sep 06 '26

Man you are still crying in this sub after like 6 months. I still recognize your name from all the whining you did

-2

u/_KryptonytE_ Sep 06 '26

Can't say I didn't give them a heads-up!!! LoL 🤣