NousResearch/hermes-agent

OAuth token refresh during credential exhaustion cooldown

Cluster 44799 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a scenario where OAuth refresh tokens expire because the refresh chain is not maintained while credentials are in an exhaustion cooldown period. The work involves keeping the refresh cycle alive even when the credential pool is temporarily exhausted.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #44853 fix(credential-pool): keep OAuth refresh chain alive during exhaustion cooldown · other
  • #44920 fix(auth): refresh OAuth tokens during exhaustion cooldown (#44799) · superseded by another PR → #44853, #44799
Closed issues · 1
  • Closed#44799Codex OAuth refresh chain not maintained while credential exhausted — refresh token expires during idle cooldown window
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

Subsystem
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.