Repository navigation
[Feature Request] Separate Aggregated vs Per-Account Usage Statistics for Multi-Account Providers (Google Antigravity) #1063
Description
Activity
Automated translation bookkeeping — detected language: unknown.
Keeping this open — the idea is wanted. The draft PR attached to this campaign was closed with specific technical feedback (see the PR thread); the ideas stay tracked here. What gets a fast review: small, rebased, independently testable slices that wire the runtime/data path first and the UI second, one concern per PR.
Keeping this open — the idea is wanted. The draft PR attached to this campaign was closed with specific technical feedback (see the PR thread); the ideas stay tracked here. What gets a fast review: small, rebased, independently testable slices that wire the runtime/data path first and the UI second, one concern per PR.
I probably won't be able to write a PR correctly. I'd be grateful if you or other participants could take care of this. Let me be the one pitching the ideas, and you, as a professional, implement them.
Consolidating this into #1062, which you filed the same day and which already carries this exact requirement.
#1062's second point asks for "Per-Account Level: Display 30-day request/token stats, current status (Ready / Quota Limited), and reset countdown timers" alongside a "Pool Level" aggregate. That is the same split this issue asks for — combined total versus per-account 30-day requests, tokens, and cost — described from the Usage tab instead of the Providers view. Building one delivers the other, so keeping both open would just mean two threads tracking a single piece of work.
Your screenshots here are the more concrete artifact of the two: 440 → 563 → 656 requests silently accumulating across two accounts is a sharper statement of the problem than the prose in #1062. That evidence is not lost — this issue stays linked from #1062 and remains readable, and the per-account breakdown work should be judged against exactly that sequence.
To be explicit about what is not being folded in: #1058 stays open on its own. Date filtering and daily per-model breakdowns are a time dimension, not an account dimension, and the two can ship independently. Same for #1060 (subscription plan expiry) and #1082 (Gem/Cla quota probes in the status check) — related area, different work, all still open.
On your note in #1062 that you would rather pitch ideas than write the PR: that is a perfectly good contribution, and reports at this level of detail are genuinely useful. It does mean these sit in the queue until a contributor picks them up, so the honest expectation is that the consolidated #1062 will move when someone takes the runtime/data path slice first and the UI second.
Follow #1062 for this. If the per-account Usage breakdown ends up scoped out of #1062 rather than delivered with it, say so there and this can be reopened as the standalone tracker.
Area
Authentication and account pool
What are you trying to accomplish?
I need OpenCodex to separate provider usage statistics into Overall Aggregated Usage (across all accounts) and Per-Account Usage (for each specific account under the provider). When switching to a newly added account (e.g., in Google Antigravity / Gemini), I need to see how many requests and tokens were consumed specifically by that active account, rather than seeing a single combined total for all accounts.
What prevents this today?
Currently, when a user starts with 1 account (which used 440 requests) and later adds a 2nd account under the same provider (Google Antigravity), the
Usagetab displays the cumulative total of all accounts combined (jumping to 563 requests, then 656 requests). OpenCodex does not split or filter usage per account, making it impossible to see the actual request/token count spent on the newly selected account versus the first account.What should OpenCodex do?
Usagetab.Example usage or interface
1. Initial State with 1st Account (440 requests)
Originally, with 1 active Google Antigravity account, 440 requests (88.6M tokens) were recorded:
2. After Adding 2nd Account — Combined Usage (563 requests)
After adding a 2nd account, the
Usagetab displays 563 requests (115.1M tokens) combined, without indicating the breakdown for the new account:3. Further Requests — Combined Usage Reaches 656 requests
As more requests are processed, the total increases to 656 requests (130.6M tokens), continuing to mix stats from all accounts together:
Alternatives or workarounds
Currently, there is no way in OpenCodex to inspect how many requests were executed by an individual account when multiple accounts are present.
Additional context
Adding a per-account filter/breakdown to the
Usagetab will allow users managing multiple Google Antigravity / Gemini accounts to accurately monitor usage per account alongside total provider consumption.Checks