Version 0.0.344 · Commit c87f222 - Possible bug in premium request counting (FIXED IN 0.0.345)

[JakeLin]

Describe the bug

After upgrading to Version 0.0.344 (Commit c87f222), I noticed that executing a single task/prompt consumed roughly 20% of my premium requests (about 60 requests). This behavior did not occur in previous versions.

Affected version

Version 0.0.344 · Commit c87f222

Steps to reproduce the behavior

1. Upgrade to Version 0.0.344.
2. Execute a prompt that runs a long task.
3. Observe the remaining premium request count during the same execution, it decreases multiple times.

Expected behavior

Only one premium request should be counted per prompt execution, regardless of task duration or complexity.

Additional context

Total usage est: 69 Premium requests
Total duration (API): 10m 12.5s
Total duration (wall): 1h 9m 4.1s
Total code changes: 1459 lines added, 188 lines removed
Usage by model:
unknown 0 input, 7.4m output, 0 cache read, 0 cache write
(Est. 69 Premium requests)

[mattchengg]

Same issue here:
one task but 41 requests.

Total usage est: 41 Premium requests
Total duration (API): 4m 53.9s
Total duration (wall): 28m 26.3s
Total code changes: 44 lines added, 11 lines removed
Usage by model:
unknown 0 input, 1.8m output, 0 cache read, 0 cache write
(Est. 41 Premium requests)

claude-sonnet-4.5 (1x)

[tat]

same here, both Haiku and Sonnet.

0.0.344
Commit: c87f222

[HarlanGIT]

Same here for claude-sonnet-4.5 (1x):

● Total usage est: 29 Premium requests
Total duration (API): 10m 51.0s
Total duration (wall): 33m 0.1s
Total code changes: 1528 lines added, 30 lines removed
Usage by model:
unknown 0 input, 3.9m output, 0 cache read, 0 cache write (Est. 29 Premium requests)

Same here, one prompt that usually took 2-3 premium requests took 29 this time. Also input, cache read/write all says 0. Something seems broken.

[nathfavour]

same here.

[RyanHecht]

Hey folks -- attempting to reproduce on my end so we can investigate this.

For people who are affected by this: do you see that many premium requests being burned on the github.com Copilot usage page? I suspect this is just a client-side rendering bug and not actually spending from your premium request usage

[ming86]

Copilot Usage shows that it is consuming my premium requests. A single prompt of haiku-4.5 in the CLI spent ~10.89 (which is 33 x 0.33) premium requests.

[HarlanGIT]

2025-10-18 copilot copilot_premium_request 29 requests

My daily report does show 29 counted requests.

[mattchengg]

Hey folks -- attempting to reproduce on my end so we can investigate this.

For people who are affected by this: do you see that many premium requests being burned on the github.com Copilot usage page? I suspect this is just a client-side rendering bug and not actually spending from your premium request usage

Yes, it also shows that many(41) premium requests on the github.com Copilot usage page

[iwangbowen]

same here

[w-m]

0.0.344
Commit: c87f222

A shorter session, the "usage by model" stats seem wrong? Using Claude Sonnet 4.5:

 Total usage est:       33 Premium requests
   Total duration (API):  3m 42.2s
   Total duration (wall): 11m 7.2s
   Total code changes:    157 lines added, 5 lines removed
   Usage by model:
       unknown              0 input, 1.3m output, 0 cache read, 0 cache write (Est. 33 Premium requests)

Just burned through > 30% of my Copilot Pro Premium requests with a few prompts. I was using copilot-cli with mcp-playwright, with --allow-all-tools.

I noticed the issue when I suddenly got an unexpected " ✗ Quota exceeded. Upgrade to increase your limit: https://github.com/features/copilot/plans".

[haithuminh]

same here, i also spent a lot of requests for a small feature