Cairn
NousResearch/hermes-agent

xAI OAuth refresh network error handling

Cluster 82204 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address unhandled network errors (such as DNS failures and connection errors) during xAI OAuth token refresh, which could surface as raw httpx tracebacks. The work involves catching and wrapping these exceptions as proper AuthError types in the CLI and auth layer.

Open issues1

  • Issue#82204[Bug]: hermes model crashes with raw httpx traceback when xAI OAuth refresh hits DNS failure

Open PRs1

  • PR#82205fix(auth): wrap xAI OAuth refresh network errors as AuthError

1 PR closed without merging

From the close comments: duplicate 1

  • #82539 fix(cli): catch httpx.ConnectError in xAI OAuth token refresh (#82204) · duplicate → #82205, #82204
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/82204.json
cluster/82204.md