NousResearch/hermes-agent

TTS response_format fallback and retry handling

Cluster 73470 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 1 PR.

These issues and fixes address how the TTS integration handles unsupported or rejected response_format values from OpenAI-compatible backends, including fallback to mp3 and retry logic.

Open issues1

  • Issue#73470[Bug]: OpenAI-compatible TTS backends that reject response_format=opus still fail after #57184

Open PRs1

  • PR#73482fix(tts): fall back to mp3 when an OpenAI-compatible backend rejects response_format (#73470)

2 PRs closed without merging

From the close comments: PR volume cleanup 1 · other 1

  • #73481 fix(tts): retry unsupported response formats · PR volume cleanup → #73482
  • #73604 fix(tts): respect backend response_format in OpenAI TTS · other → #73604, #73482
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

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.