Surface provider quota and account limits in UI
NousResearch/hermes-agent · cluster 7714 · agent
Data as of
10 open items. Fix merged in #115766. Check it covers your case.
The short answer
- Known?
- Yes. 24 related items grouped here, 6 issues already closed.
- Fix event
- A fix was merged to main in PR #115766. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PRs #115766, #115899. That is separate from the fix event. - Still open
- 6 issues and 4 PRs.
Next step: read #115766, then check whether your report is one of the 6 still open.
Read #115766Pick up a Lab taskThese issues and PRs concern displaying provider quota, rate-limit, and account-limit data (especially for OpenAI Codex) across CLI, TUI, and Desktop interfaces via /status and /usage commands. A recurring sub-theme involves credential resolution bugs where Codex OAuth tokens stored in credential_pool are not correctly surfaced to the usage and gateway layers.
Open issues6
- Issue#7714[Feature]: why /status command does not like openclaw that shows the usage and when to reset
- Issue#9085[Feature]: surface OpenAI Codex plan-limit headers in /usage (5h / 7d windows, plan, credits)
- Issue#16643Show provider account limits in the TUI status bar
- Issue#21814Add `hermes usage` CLI command and agent-accessible quota tool
- Issue#42873Feature: Self-tracked provider quota display in /status
- Issue#53306feat(cli): show provider quota and rate-limit in status bar for all providers
Open PRs4
Fixes on record
-
#115766 fix(usage): Codex quota windows labelled correctly and shown on every /usage surface (#65387, #42904, #15167, #79695; salvage #65400, #42905)
files:
agent/account_usage.py,apps/desktop/src/app/session/hooks/use-prompt-actions/utils.test.ts,apps/desktop/src/app/session/hooks/use-prompt-actions/utils.ts,contributors/emails/[redacted:email],gateway/slash_commands_status.py,hermes_cli/cli_info_mixin.py,tests/agent/test_account_usage.py,tests/gateway/test_usage_command.py,tests/hermes_cli/test_cli_status_bar.py,tests/tui_gateway/test_session_usage_account_lines.py,tui_gateway/methods_session.py -
#115899 feat(cli): `hermes usage --json` prints Codex quota windows without a session (#33094, salvage #81819)
files:
hermes_cli/main.py,hermes_cli/subcommands/usage.py,tests/hermes_cli/test_usage_command.py,website/docs/reference/cli-commands.md
6 PRs closed without merging
From the close comments: superseded by another PR 2 · merged via another change 1 · other 3
-
#15173 fix(auth/gateway): surface Codex OAuth credential from credential_pool to /usage (#15167) · superseded by another PR →
#17480 -
#16644 feat(tui): show account limits in status bar · superseded by another PR →
#16652 - #17480 fix(auth): resolve Codex usage credentials from auth fallbacks · other
-
#42905 fix: show account limits for persisted usage · merged via another change →
604d880,#115766,#65387,#42904,#15167,#79695,#65400,#42905 -
#93282 feat(cli): show official OAuth quota via hermes usage · other →
9f98932
Show 1 more
- #116605 feat(usage): surface Codex plan-limit windows · other
Closed issues · 6
- Closed#15167/usage shows no Codex account quota; _read_codex_tokens() ignores credential_pool
- Closed#32730hermes auth add openai-codex writes only to credential_pool; runtime resolver reads providers.tokens — fails with 'missing access_token'
- Closed#33094Expose remaining OpenAI Codex subscription usage in Hermes CLI
- Closed#42904Desktop /usage no-agent fallback omits Codex account limits and reset
- Closed#45713[Feature]: In the new Hermes Desktop app, typing /usage only shows the Nous credits block, even when the active provider is OpenAI Codex / GPT-5.5. The Codex account-limit data is available in Hermes, but Desktop does not appear to surface it.
- Closed#57476Expose OpenAI Codex subscription quota in status and gateway slash command
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.07: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab