Skip to content

fix(monitoring): allow Codex quota refresh without account id#87

Merged
seakee merged 2 commits into
mainfrom
fix/codex-quota-optional-account-id
May 14, 2026
Merged

fix(monitoring): allow Codex quota refresh without account id#87
seakee merged 2 commits into
mainfrom
fix/codex-quota-optional-account-id

Conversation

@seakee
Copy link
Copy Markdown
Owner

@seakee seakee commented May 14, 2026

Summary

Fix Codex quota refresh in request monitoring when credentials do not expose a ChatGPT account ID.

Cause

Request monitoring had a separate Codex quota request path that still required chatgpt_account_id.
Other quota paths had already made Chatgpt-Account-Id optional, so the behavior drifted.

Solution

  • Add shared Codex quota request helpers with optional Chatgpt-Account-Id.
  • Add shared Codex quota parsing and rate-limit helpers.
  • Move quota cards, request monitoring, and Codex inspection onto the shared helpers.
  • Add regression coverage for Codex quota targets without account IDs.

Testing

  • npm test -- codexQuota accountOverviewQuotaTargets MonitoringCenterPage
  • git diff --check
  • npm run type-check currently fails on existing missing react-test-renderer / type declarations in unrelated auth-file tests.

seakee added 2 commits May 14, 2026 10:49
Extract shared Codex quota request, parsing, and rate-limit helpers.

Move quota page and Codex inspection onto the shared path.

Keeps existing behavior while reducing future drift across callers.
Remove the request monitoring hard failure when Codex credentials lack a ChatGPT account ID.

Use the shared optional-header Codex quota request helper.

Adds regression coverage for account-id-less Codex quota targets.
@seakee seakee merged commit 7b73989 into main May 14, 2026
3 checks passed
@seakee seakee deleted the fix/codex-quota-optional-account-id branch May 14, 2026 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant