Skip to content

[app-server] Expose rate-limit reset credit details#30395

Open
jayp-oai wants to merge 1 commit into
mainfrom
codex/reset-credit-details
Open

[app-server] Expose rate-limit reset credit details#30395
jayp-oai wants to merge 1 commit into
mainfrom
codex/reset-credit-details

Conversation

@jayp-oai

@jayp-oai jayp-oai commented Jun 28, 2026

Copy link
Copy Markdown
Collaborator

Why

Supported clients currently receive only the reset-credit count from account/rateLimits/read. The redemption UI needs the available credits, their expiry times, and a way to consume the credit the user selected without accessing private backend APIs directly.

What changed

  • add the v2 account/rateLimitResetCredit/list RPC
  • return the full availableCount plus up to 10 detail rows, matching the backend response cap
  • keep account/rateLimits/read unchanged and count-only
  • add an optional nullable creditId to account/rateLimitResetCredit/consume; omitting it preserves the existing automatic selection behavior
  • forward a selected credit ID to the Codex backend and map the detail response into the app-server protocol
  • update the app-server README and generated schema fixtures

The TUI consumer is stacked in #30488.

Validation

  • just test -p codex-app-server-protocol (251 passed)
  • just test -p codex-backend-client (16 passed)
  • just test -p codex-app-server rate_limit_reset_credit (9 passed)
  • just test -p codex-tui chatwidget::tests::usage (29 passed compatibility check)
  • just fix -p codex-backend-client -p codex-app-server-protocol -p codex-app-server -p codex-tui
  • just fmt
  • Autoreview: clean

Part of #29618.

@jayp-oai jayp-oai force-pushed the codex/reset-credit-details branch from faed994 to 136386e Compare June 28, 2026 22:55
@jayp-oai jayp-oai changed the title [codex] Show usage-limit reset expiry details [app-server] Expose rate-limit reset credit details Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant