NousResearch/hermes-agent

xAI streaming TTS API key vs OAuth priority bug

Cluster 113727. Data as of 2026-10-24 13:18 UTC

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

open issues

open PRs

items grouped

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

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

Read #114821 Pick up a Lab task

A bug where xAI streaming TTS incorrectly prefers OAuth bearer tokens over an explicitly set XAI_API_KEY, resulting in 403 errors. The related items address fixing the authentication priority order.

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.

#114821 fix(tts): xAI streaming TTS uses XAI_API_KEY over the subscription OAuth bearer (#113727, salvage #113728)

merged to main

files: hermes_cli/setup_tts.py, tests/hermes_cli/test_setup_tts_xai_oauth.py, tests/tools/test_tts_streaming.py, tools/tts_streaming.py, tools/tts_tool.py, website/docs/developer-guide/streaming-tts.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#113728 fix(tts): prefer explicit XAI_API_KEY over subscription OAuth in streaming TTS · merged via another change → 27a30d8, #114821, #113727, #113728
#113985 fix(tts): xAI streaming TTS must prefer XAI_API_KEY over OAuth bearer · superseded by another PR → 27a30d8, #114821, #113727, #113728

Closed issues · 1

Closed#113727Bug: xAI streaming TTS resolves OAuth-first and 403s even when XAI_API_KEY is set

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.50: 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: #114821
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/113727.json
cluster/113727.md