# NousResearch/hermes-agent · Auto-TTS voice reply failures across platforms

## Open now

- 2 issues, 0 PRs open on GitHub.
- #13126: \`\[Bug\]: Slack — TTS voice reply never sent after voice input (_should_send_voice_reply always returns False)\`
- #51282: \[Bug\]: Discord DM voice messages transcribe correctly but no auto-TTS voice reply is sent when chat voice mode is \`voice_only\`

Multiple bugs and fixes address auto-TTS voice replies being silently skipped or incorrectly suppressed across Discord, Slack, Telegram, and the gateway layer, particularly under streaming, voice-only mode, and tool-call conditions.

## TL;DR

- 7 member(s): 2 open issue(s), 2 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #73508. Verify it addresses your case.
- **Recommended:** read PR #73508 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `partially_resolved` · deciding PR(s): `pr-73508`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): 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.24`: the share of member 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.

## Open related issues

- #13126: \`\[Bug\]: Slack — TTS voice reply never sent after voice input (_should_send_voice_reply always returns False)\`
- #51282: \[Bug\]: Discord DM voice messages transcribe correctly but no auto-TTS voice reply is sent when chat voice mode is \`voice_only\`

## Closed / duplicate issues

- #23983: Auto voice reply silently dropped on long-running voice-in turns (streaming + tool calls)
- #51867: \[Bug\]: Telegram voice replies skip auto-TTS when response is streamed

## Prior & competing PRs

- **#13329: fix(slack): allow voice replies after voice input**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `4bda9dcade8bf1080a6c70841fe862f8c7229c00`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#73508: fix(gateway): platform-aware auto-TTS voice delivery (opus platforms, streamed/global gap, captions)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - files: `contributors/emails/[redacted:email]`, `contributors/emails/[redacted:email]`, `contributors/emails/[redacted:email]`, `gateway/platforms/base.py`, `gateway/run.py`, `plugins/platforms/feishu/adapter.py`, `plugins/platforms/matrix/adapter.py`, `plugins/platforms/telegram/adapter.py`, `tests/gateway/test_auto_voice_reply_format.py`, `tests/gateway/test_base_auto_tts_output_format.py`, `tests/gateway/test_matrix_voice.py`, `tests/gateway/test_telegram_voice_caption_markdown.py`, `tests/gateway/test_voice_command.py`, `tests/tools/test_tts_opus_routing.py`, `tools/tts_tool.py`
- **#51859: fix(gateway): auto tts voice message replies**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `f440a44753`, `#73508`, `#62040`, `#73508`

## Fix status

- Merged to main in PR #73508 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-07-28`.
- Subsystem: `gateway`