NousResearch/hermes-agent

Codex pool false quota-exhausted from ms timestamps

Cluster 103349. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #115767 on 19 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #115767. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #115767. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #115767, then check it covers your case.

Read #115767 Pick up a Lab task

These items concern a bug where millisecond-precision last_error_reset_at timestamps or expired probe tokens cause healthy Codex pool credentials to appear quota-exhausted, silencing the agent with false 429 errors. The members propose or discuss fixes to prevent valid accounts from being incorrectly marked as exhausted.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#115767 fix(auth): Codex pool stops spinning and false 'quota exhausted' on ms reset timestamps or expired probe tokens (#97315, #103349, #89415; salvage #97328, #103356)

merged to main

files: agent/credential_pool.py, agent/credential_pool_admin.py, hermes_cli/auth.py, hermes_cli/auth_codex.py, tests/agent/test_credential_pool.py, tests/agent/test_credential_pool_sole_rotate_recovery.py, tests/hermes_cli/test_auth_codex_quota_probe.py, website/docs/user-guide/features/credential-pools.md

1 PR closed without merging

From the close comments: merged via another change 1

#103356 fix(auth): stop healthy Codex pool accounts from appearing quota-exhausted · merged via another change → 4c3d31e, #115767, #97315, #103349, #89415, #97328, #103356

Closed issues · 1

Closed#103349Codex pool: millisecond `last_error_reset_at` hides a usable credential — agent goes mute with false "quota exhausted (429)"

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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

At a glance

Merged PRs: #115767
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/103349.json
cluster/103349.md