fix(usage): read and redeem hub reset credits through CLIProxyAPI

[juliusmarminge]

CLIProxyAPI accounts could show usage windows without their banked reset credits. T3 read a custom quota-scheduler endpoint and only allowed native provider instances to redeem credits.

Use the built-in auth-files and api-call management endpoints for account discovery, Claude/Codex usage, and Codex credit reads and redemption. Pin redemption to the displayed credit with a stable request ID, handle the upstream outcome, clear the account's routing cooldown through reset-quota, and publish refreshed limits. Web, desktop, and mobile use the same target through the Usage page and composer panel. No hub plugin is required.

Validation: 51 focused tests pass; server, web, and client-runtime typechecks and targeted lint pass. Read-only verification against a live hub returned four Claude accounts and both Codex accounts with two credits each. Browser redemption used a disposable fixture, not real credits. Mobile typecheck reports the same 59 navigation errors as the base revision; no new errors. Native mobile runtime was not exercised.

CI is green on the current head. Automated correctness review is unavailable: Cursor Bugbot is paused at its spend limit, and Macroscope returned a neutral approvability check because its monthly review budget is exhausted. No inline review findings are open.

Before, both hub accounts lack credit counts:

After, both hub accounts show two credits:

Confirmed redemption and refreshed balance, using fixture data

Implemented with GPT-6 in Codex.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This change adds a substantial CLIProxyAPI integration that reads provider auth accounts, exposes banked credits, and performs irreversible external redemption plus cooldown-clearing actions. It also changes the existing configured-hub read path and wires the behavior through server RPC, shared aggregation, web, and mobile surfaces.

Not approved because:

• Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+10 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	8	8	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.5 KiB	−17 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.1 KiB	7.0 KiB	−12 B (−0.2%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−5 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.8 KiB	57.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	8	8	0 (0.0%)	21	✅

Baseline: 9a47c7b · PR result: 5d7152e · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.9 KiB
• Claude decoded thread snapshot: 114.6 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.