Yup was getting this too ... suddenly x3 rate instead of x1

Yeah whatever happened to this BS? As the famous saying goes, "So that was a F'ing lie".

Can confirm. This was slipped in on the sly. I didn't even realize I was burning 3x...just noticed that my percentage was going up fast and then bam 3x...wow.

I’m seeing the same thing too : Opus 4.5 is suddenly being counted at 3× instead of the 1× promo rate, so it’d be great if the team could check whether something’s off.

Just saw my quota being completely exhausted. Then realized that Claude Opus 4.5 is using 3X tokens.
Can we please look into this? a quick reset of the premium request usage?

It is now confirmed 3x, allthough after refreshing it does not even show up in the model list. But before that it definitely was there as 3x

"Just yesterday I ran out of credits. I was doing great with Opus 4.5 because it was giving me excellent results, so I decided to upgrade from the Pro plan ($100 per year) to the Pro+ plan for $390 (4×). And of course, I was super happy about it. Today I wake up and see that Opus 4.5, my star model, is now at 3×. What a bummer — I barely got to enjoy it. Now I’m checking the plans and Opus 4.5 doesn’t even appear in the Pro plan anymore, only in Pro+. I don’t know what to do: downgrade back to Pro or stay on Pro+. I’m not a programmer, I just do this as a hobby, and $390 feels like a lot."
"I’m still thinking about it — whether to switch back to Pro or wait to see if Microsoft lowers it from 3× to 2× or less. Or maybe Google or OpenAI will release a better model. For now, GPT 5.1 Codex Max seems like an excellent alternative; it even surpasses Opus 4.5 in many aspects."

claude opus 4.5 beats everything. i am so sad that went 3x. i am a bit of vibing with vscode. i am not a programmer. i am saying my thoughts to opus and just does what i want perfectly.

Hello team,
This issue, where the request multiplier for Claude Opus 4.5 jumped from the promotional 1x to 3x, is clearly a backend billing or configuration anomaly, but its impact points to a potential traffic surge that should be independently verified.

Service Monitoring & Alerting: The immediate detection of a sudden, drastic spike in "premium request usage" by users, while "actual request consumption" remained stable, suggests a successful billing configuration change (intended or accidental). From a network perspective, we need to confirm if our edge network monitoring (load balancers, WAFs, traffic flow logs) registered a corresponding 3x increase in API calls or if the change was purely internal to the consumption engine.

Latency Impact: A sudden increase in the perceived "cost" per request might drive a large number of users to switch models or reduce usage, potentially altering network traffic patterns. If the 3x multiplier was pushed out without appropriate capacity planning, it could signal an attempt to throttle usage that might indirectly introduce service latency if the underlying infrastructure is saturated.

Audit Trail: The core issue is an unannounced configuration change affecting user billing. We need to confirm that the internal change control logs align with the reported time of the multiplier change, ensuring that the appropriate security and financial audit trail is intact.

Recommendation: The GitHub team needs to Rollback the 3x multiplier immediately and communicate the root cause. Concurrently, a full traffic analysis should be executed to differentiate between a simple multiplier misconfiguration and a true service scaling anomaly caused by increased usage.

This is very bad from GitHub. Has anyone tried Kilocode? It's ruining our $20 plan. How many requests do you give it?

This is really devious stuff, IMO. I only just happened to notice the x3 tonight. Checked my premium usage and I'm nearly out of credits already. There should've been some more obvious warning that they were going to change the rate a few days into the billing cycle.

Anyway, brilliant as Claude Opus is, it's not worth x3 times the other premium models.

I didn't receive any notification either. I was using it 1x last week, today it became 3x and most of my quota is gone.

It is helpful that I checked this issue. I was wondering why my quota had gone way up today. I'm a Heavy user, and this is not something I like very much, this is an ongoing issue with the team and the releases, The lack of transparancy between the users and the devs of Copilot. It seems that major changes are occuring backend, and the lack of transparancy within the application itself is not very cool.
They need to start to communicate on policies changes and on fixes, bugs, and overall features.

Agree. My credits ran out because this jumped up to 3x instead of 1x without any warning or notification to me! It just changed out of nowhere! I don't know how github can claim to run a business if they are screwing their users out of the requests they pay for

I am going to look into cursor. Regardless of everything else, I dont think they play games where they screw their users out of credits without any warning

wait what, I just noticed it right now. This is ridiculous

its back with 3x

Completely busted my monthly limit by not realizing that it was increased to 3x. This should be communicated better.

I would like to add my experience as well, because this situation raises a serious transparency and budgeting issue.

When I purchased Copilot Pro+ for the entire year, the model selector clearly showed Claude Opus 4.5 at 1×. This was presented as one of the main benefits of the Pro+ tier and it was a decisive factor in choosing the higher subscription.

Just two days after paying for the annual plan, the multiplier silently changed to 3× without any form of notification — no banner, no popup, no email, no in-product alert. The only way to notice the change was to manually reopen the model dropdown, which users do not regularly do when a model is already selected.

If the multiplier is going to change from 1× to 3×, this is precisely the kind of update that must be clearly communicated in advance, especially because it directly impacts:

user budgeting,

monthly usage planning,

expectations set at the moment of purchase,

and the real value of the subscription.

Failing to inform users about a 300% price increase creates an entirely avoidable situation where paid quota is depleted unexpectedly — which is exactly what happened in my case. This is not acceptable for a paid professional service.

Promotional rates (1×) must be clearly labeled as temporary, with an expiry date or at least an in-product notice. And any increase to 3× must be announced prominently to avoid budget issues and surprise over-consumption.

The problem is not the 3× multiplier itself.
The problem is the lack of transparent, proactive communication, which directly affects paying customers.

I sincerely hope the team will acknowledge this issue, reset affected premium usage, and commit to improving the communication flow for all future pricing changes.

Suggestion to the copilot team, next time when you show 1x as a discounted price, please find a way to label it clearly. So we can anticipate the change and not blow our wallet by accident.

Yes pretty sneaky putting it on at 1x and not giving any clear indication that it had changed or was going to change.