NousResearch/hermes-agent

STT/TTS config api_key and base_url ignored

Cluster 4102 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

A bug where api_key and base_url from STT (and TTS) config are not read for local endpoints, causing provider selection to fail or treat placeholder keys as valid. Multiple fixes and related reports address this same configuration-reading issue.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #4103 fix(tools): read api_key and base_url from stt.openai config for local endpoints · done elsewhere → 28380e7
  • #4209 fix: read stt/tts api_key and base_url from config for local endpoints · other
Closed issues · 1
  • Closed#4102bug(tools): stt.openai.api_key and base_url from config are ignored — STT provider always MISSING for local 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.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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.