TTS config.yaml API key/URL not being read

NousResearch/hermes-agent · cluster 26175 · agent

Data as of 2026-10-23 11:54 UTC

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

open issues

open PRs

items 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 resolved, deciding PR #73512. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #73512 Pick up a Lab task

A bug where the TTS subsystem ignores tts.openai.api_key and tts.openai.base_url set in config.yaml, preventing config-only setups from reaching self-hosted endpoints. Multiple fix attempts address reading these values from config before falling back to environment variables.

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: duplicate 2 · other 1

#26209 fix(tts): read tts.openai.api_key/base_url from config.yaml before env vars · other → b53ba0e
#26218 fix(tts): read tts.openai.api_key/base_url from config.yaml before env vars · duplicate → #26209, #13888, #4209, #26175
#26233 fix(tts): honor config-only OpenAI audio endpoints · duplicate → #13888, #4209, #26209, #26175

Closed issues · 1

Closed#26175TTS tool ignores `tts.openai.api_key` / `tts.openai.base_url` in `config.yaml` — config-only setups cannot reach self-hosted endpoints

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: agent
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/26175.json
cluster/26175.md