Regression: custom provider rate limits no longer appear in /status
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
After updating Codex CLI to 0.154.0, /status no longer displays limits supplied by a custom provider. It shows Limits: data not available yet, although this worked previously.
Commit 5037919777 (#42372) changed the TUI to populate status limits only from AccountUsage snapshots, ignoring streamed RollingUpdate snapshots. However, account usage refresh is disabled for custom providers using API-key authentication, leaving no way for their streamed limits to populate /status.
Could streamed rate limits remain available for display when account usage refresh is unavailable? Preserving authoritative account data should not prevent custom providers from displaying their own limits.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing commit 5037919777 (#42372) and the TUI code that populates /status from AccountUsage and RollingUpdate snapshots. Trace the custom-provider API-key path where account usage refresh is disabled. Done means streamed custom-provider limits appear in /status while authoritative account data remains preferred when available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100