00345 and 00346 still displays wrong request count at the end of the session!

[ahmetus]

Describe the bug

It does fixed with Version 0.0.345 if you look to your usage at your github profile, but still after finishing two hours Haiku session, it said 124 premium requests for my usage, luckly it looked as 4.25 requests on my github profile. But it worried me, so, there is still usage display issue at the end of the session!

Affected version

0.0.345 Commit: 470f8be

Steps to reproduce the behavior

1- Create a copilot session.
2- Work
3- Finish the session, look at the message that contains usage information when you exit from copilot

Expected behavior

Expected behavior is counting requests wrongly after finishing session

Additional context

No response

[andyfeller]

@ahmetus : thank you for reporting this concern! 🙇 I'd like to confirm whether this is 0.0.345 or the newly released 0.0.346 we released earlier this afternoon to address usage reporting.

[ahmetus]

@ahmetus : thank you for reporting this concern! 🙇 I'd like to confirm whether this is 0.0.345 or the newly released 0.0.346 we released earlier this afternoon to address usage reporting.

It looks like it has still issues with 0.0.346, because after completing small bug session in total 27 minutes, it still displayed 18 premium request, here is the cli output after completing session and closing the copilot :

● Total usage est: 18.15 Premium requests
Total duration (API): 6m 7.0s
Total duration (wall): 27m 52.0s
Total code changes: 207 lines added, 9 lines removed
Usage by model:
claude-haiku-4.5 0 input, 4.9m output, 0 cache read, 0 cache write (Est. 18.15 Premium requests)

But my github billing profile says total 3 premium requests, and my percentage also confirms that. So, it does not effect the final outcome, but it worries to user.

What is great about copilot is, tool calling works perfectly and with models like Haiku, it is speedy and performant, that part enjoyable, better than codex, it is an achivement. It seems it optimized perfectly for agentic work. But it still has some basic missing features that all other cli tools have. So, congrats but you have a long way to walk.

[EvanBoyle]

@ahmetus we have a PR in review that fixes the client-side display of PRUs, but rest assured we have verified that correct billing information is being recorded server-side as of the .345 release. We will cut a release later today that fixes the client side display bug.

I am going to close this issue as a duplicate of #351 which I have reopened and will leave open until we rectify any overbilling that may have occurred.