Cairn
NousResearch/hermes-agent

OpenAI TTS streaming ignores custom base_url config

Cluster 73530 · skills. Data as of

Nothing open on GitHub. Fix merged in #73512. Check it covers your case.

The short answer

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

Multiple reports and fixes address OpenAIStreamer not respecting the tts.openai.base_url (and related api_key) configuration, causing streaming TTS requests to go to api.openai.com instead of the configured endpoint.

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.

  • #73512 fix(tts): honor config.yaml endpoints across all providers + bounded upstream buffering

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], tests/tools/test_tts_model_cache_lru.py, tests/tools/test_tts_openai_config.py, tests/tools/test_tts_provider_base_urls.py, tests/tools/test_tts_response_body_cap.py, tests/tools/test_tts_streaming.py, tests/tools/test_tts_xai_speech_tags.py, tools/tts_streaming.py, tools/tts_tool.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1

  • #73533 fix(tts): honor tts.openai.base_url/api_key in the streaming path (#73530) · done elsewhere → 7800bb1, #47588, #73530
  • #73536 fix(tools): honour tts.openai.base_url in the streaming path · superseded by another PR → #73512, #70307
  • #73589 fix(tts): use tts.openai.base_url config in OpenAIStreamer · done elsewhere → 861c2fe, #73530
Closed issues · 1
  • Closed#73530OpenAIStreamer ignores tts.openai.base_url, so streaming TTS escapes to api.openai.com
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.40: 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
skills
Merged PRs
#73512
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.

cluster/73530.json
cluster/73530.md