Cairn
NousResearch/hermes-agent

xAI OAuth auxiliary client wrong API endpoint fix

Cluster 34171 · agent. 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.

The xAI OAuth auxiliary client was incorrectly routed to the Responses API instead of chat completions, causing 403 errors on certain operations. These members address identifying and correcting that misconfiguration.

Open issues1

  • Issue#34171xai-oauth auxiliary client incorrectly uses Responses API (CodexAuxiliaryClient), causing 403 on compression/vision/web_extract

Open PRs1

  • PR#34241fix(aux): keep xai oauth auxiliary on chat completions

1 PR closed without merging

From the close comments: duplicate 1

  • #34376 fix(auxiliary): xai-oauth uses chat.completions, not Responses API (#34171) · duplicate → #34241
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/34171.json
cluster/34171.md