feat: track provider usage and project weekly quota by Aditya190803 · Pull Request #1605 · pingdotgg/t3code

Aditya190803 · 2026-03-31T11:07:48Z

What Changed

Added provider usage normalization and merge utilities for Codex/Claude quota payloads.
Extended provider snapshots and websocket config/update flow to carry normalized usage buckets.
Fixed usage percent math to avoid double-scaling low percentages derived from usage/limit.
Fixed usage cache merge behavior so stale cached usage is dropped when a newer provider snapshot omits usage.
Added/updated tests covering usage normalization, merge behavior, and stale cache handling.

Why

Issue #228 asks for accurate quota visibility. This PR adds provider usage projection and makes it robust under incremental updates so UI quota values stay correct. The follow-up fixes address reviewer-reported edge cases that could misreport low usage percentages or retain stale usage after newer snapshots.

UI Changes

Settings provider quota bars now render normalized usage/reset data from provider snapshots.
No layout redesign.

Checklist

This PR is small and focused
I explained what changed and why
I included before/after screenshots for any UI changes
I included a video for animation/interaction changes

Closes #228

Note

Track provider usage quotas and display weekly/5-hour usage buckets in settings

Adds normalizeProviderUsageFromRateLimits in providerUsage.ts to derive standardized ServerProviderUsageBucket records from heterogeneous Codex and Claude rate-limit payloads.
Extends Claude and Codex provider probes to collect rate-limit data and return account, rateLimits, and derived usage fields on the ServerProvider snapshot.
The WebSocket server maintains a per-provider usage cache, merges incremental account.rate-limits.updated events, and pushes serverProvidersUpdated only when usage materially changes.
Adds ProviderUsageRows to the settings UI to render a progress bar, remaining percentage, and reset timestamp for each usage bucket.
Behavioral Change: serverGetConfig and serverRefreshProviders responses now include provider usage fields; stale cached usage is dropped when the provider snapshot has a newer timestamp.

^{Macroscope summarized 6b8ed4d.}

Note

Medium Risk
Touches provider probing and WebSocket provider update logic to ingest and cache rate-limit events; bugs here could cause incorrect quota display or extra/missed serverProvidersUpdated pushes.

Overview
Adds end-to-end provider quota/usage tracking by extending ServerProvider snapshots with optional account, rateLimits, and normalized usage buckets (weekly/5-hour).

Codex and Claude probes now collect rate-limit payloads (Codex via account/rateLimits/read + account/rateLimits/updated, Claude via SDK rate_limit_event capture), normalize them via new normalizeProviderUsageFromRateLimits, and attach derived usage to provider status.

The server now maintains a per-provider usage cache that merges incremental account.rate-limits.updated runtime events, drops stale cached usage when newer provider snapshots omit it, and only pushes server.providersUpdated when usage materially changes; the settings UI renders these buckets as progress bars with remaining percent and reset time.

^{Written by Cursor Bugbot for commit 6b8ed4d. This will update automatically on new commits. Configure here.}

coderabbitai · 2026-03-31T11:07:56Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7d94fdf2-6028-43be-8f44-f60835306908

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

apps/server/src/provider/providerUsage.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 11eab91d87

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-31T11:17:41Z

apps/server/src/wsServer.ts

+    const mergedUsage = mergeProviderUsage(cachedUsage, provider.usage);
+    if (mergedUsage !== undefined) {
+      nextCache[provider.provider] = mergedUsage;
+      continue;


Drop stale usage cache when provider snapshot has no usage

In mergeUsageCacheFromProviders, stale entries are never evicted because mergeProviderUsage(cachedUsage, provider.usage) returns cachedUsage whenever the new snapshot omits usage, so the mergedUsage !== undefined branch always keeps the cache and bypasses shouldKeepCachedUsage. This means a newer provider snapshot (checkedAt later than cached updatedAt) can still be served with outdated quota buckets via serverGetConfig and server.providersUpdated.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-03-31T11:17:41Z

apps/server/src/provider/providerUsage.ts

+  if (limit !== null && limit > 0) {
+    return normalizePercent((usage / limit) * 100);


Avoid double-scaling low usage percentages

derivePercentFromUsage converts absolute usage to percent with (usage / limit) * 100, then passes that result to normalizePercent, which multiplies any value <= 1 by 100 again. For low-but-valid percentages (for example usage=1, limit=1000), this reports 10% instead of 0.1%, causing major quota misreporting near the start of a window.

Useful? React with 👍 / 👎.

apps/server/src/wsServer.ts

apps/server/src/provider/providerUsage.ts

apps/server/src/provider/codexAppServer.ts

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

cursor · 2026-04-01T06:01:22Z

apps/server/src/provider/codexAppServer.test.ts

+      planType: "pro",
+    });
+    expect(state.rateLimits).toBeNull();
+  });


Grace period exceeds test abort timeout causing rejection

High Severity

The test passes AbortSignal.timeout(1_000) (1s) but RATE_LIMITS_PROBE_GRACE_MS is 1_500 (1.5s). When the stub ignores account/rateLimits/read, the grace timer starts after the account snapshot is set. The abort signal fires at ~1s — before the 1.5s grace timer resolves rateLimitsPayload to null — causing fail() to reject the promise with an abort error instead of the expected successful resolution.

Additional Locations (1)

apps/server/src/provider/codexAppServer.ts#L25-L26

… cache updates

Aditya190803 · 2026-04-01T06:18:00Z

I cleaned up the branch history to reduce review noise and make the change set easier to reason about.

What changed:

Rebased onto latest main.
Removed merge/sync churn from feature history.
Squashed follow-up fixups into logical commits.
Kept implementation scope unchanged (no new feature surface beyond already discussed fixes).

Current commit structure:

feat(contracts): add normalized provider usage and quota bucket schemas
feat(server): normalize provider rate-limit usage and stabilize usage cache updates
feat(web): render provider quota usage buckets in settings

Behavior/correctness included in this cleaned history:

Fix low-percent double-scaling risk in usage normalization.
Drop stale cached usage when newer provider snapshots omit usage.
Clamp over-limit utilization and suppress no-op provider update pushes.
Preserve tests across contracts/server/web for quota projection and cache behavior.

Validation run locally:

bun fmt
bun lint
bun typecheck

No functional intent change; this is primarily a history hygiene pass for clearer review.

juliusmarminge · 2026-04-01T07:24:04Z

Please add screenshots

github-actions bot added size:XL 500-999 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Mar 31, 2026

Aditya190803 marked this pull request as draft March 31, 2026 11:08

Aditya190803 marked this pull request as ready for review March 31, 2026 11:13

macroscopeapp bot reviewed Mar 31, 2026

View reviewed changes

apps/server/src/provider/providerUsage.ts Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 31, 2026

View reviewed changes

cursor bot reviewed Mar 31, 2026

View reviewed changes

apps/server/src/wsServer.ts Outdated Show resolved Hide resolved

apps/server/src/provider/providerUsage.ts Show resolved Hide resolved

cursor bot reviewed Apr 1, 2026

View reviewed changes

apps/server/src/provider/codexAppServer.ts Show resolved Hide resolved

github-actions bot added size:XXL 1,000+ changed lines (additions + deletions). and removed size:XL 500-999 changed lines (additions + deletions). labels Apr 1, 2026

cursor bot reviewed Apr 1, 2026

View reviewed changes

Aditya190803 added 3 commits April 1, 2026 11:34

feat(contracts): add normalized provider usage and quota bucket schemas

6b4aac4

feat(server): normalize provider rate-limit usage and stabilize usage…

b2025a3

… cache updates

feat(web): render provider quota usage buckets in settings

6b8ed4d

Aditya190803 force-pushed the feat/weekly-usage branch from 2c50e2d to 6b8ed4d Compare April 1, 2026 06:05

Aditya190803 mentioned this pull request Apr 1, 2026

feat: add usage / quota visibility for Codex sessions and accounts #228

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: track provider usage and project weekly quota#1605

feat: track provider usage and project weekly quota#1605
Aditya190803 wants to merge 3 commits intopingdotgg:mainfrom
Aditya190803:feat/weekly-usage

Aditya190803 commented Mar 31, 2026 •

edited by cursor bot

Loading

Uh oh!

coderabbitai bot commented Mar 31, 2026 •

edited

Loading

Review skipped

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 31, 2026

Uh oh!

chatgpt-codex-connector bot Mar 31, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot left a comment

Uh oh!

cursor bot Apr 1, 2026

Uh oh!

Aditya190803 commented Apr 1, 2026

Uh oh!

juliusmarminge commented Apr 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		if (limit !== null && limit > 0) {
		return normalizePercent((usage / limit) * 100);

Conversation

Aditya190803 commented Mar 31, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What Changed

Why

UI Changes

Checklist

Track provider usage quotas and display weekly/5-hour usage buckets in settings

Uh oh!

coderabbitai bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor bot Apr 1, 2026

Choose a reason for hiding this comment

Grace period exceeds test abort timeout causing rejection

Uh oh!

Aditya190803 commented Apr 1, 2026

Uh oh!

juliusmarminge commented Apr 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Aditya190803 commented Mar 31, 2026 •

edited by cursor bot

Loading

coderabbitai bot commented Mar 31, 2026 •

edited

Loading