Cairn
NousResearch/hermes-agent

Generic streaming TTS support for CLI voice mode

Cluster 47896 · agent. Data as of

1 open item. Fix merged in #73862 on 29 Jul 2026. Check it covers your case.

The short answer

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

These members all concern streaming text-to-speech: using the TTSProvider.stream() method generically in CLI voice mode, since plugin providers define it but dispatch and the CLI reportedly do not consume it. One also mentions clause-by-clause synthesis and gateway adapters.

Open issues1

  • Issue#47896Plugin TTS providers define stream(), but current TTS dispatch and CLI never consume it generically

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #73862 feat(voice): streaming TTS — clause-by-clause synthesis for CLI voice mode and gateway adapters

    merged to main

    files: contributors/emails/[redacted:email], docs/streaming-tts.md, gateway/platforms/base.py, gateway/run.py, gateway/streaming_tts_consumer.py, hermes_cli/voice.py, tests/gateway/test_streaming_tts_consumer.py, tests/gateway/test_streaming_tts_gateway_regression.py, tests/hermes_cli/test_voice_wrapper.py, tests/tools/test_tts_streaming.py, tests/tools/test_tts_streaming_e2e.py, tools/tts_streaming.py

Closed issues · 1
  • Closed#58930Feature request: make CLI voice mode use generic TTSProvider.stream()
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
#73862
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
29 Jul 2026

For your agent

The same facts, typed.

cluster/47896.json
cluster/47896.md