# NousResearch/hermes-agent · Desktop auto-TTS double-read bug and fix

## Open now

- Nothing open on GitHub.

A bug was identified where auto-TTS would speak the same reply twice under a specific timing edge case during playback idle. The cluster includes the bug report and related fix attempts targeting the race condition in the auto-speak replies logic.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: 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.

## Closed / duplicate issues

- #102960: \[Bug\] Desktop auto_tts double-read: same reply spoken twice when message arrives during playback idle edge

## Prior & competing PRs

- **#102970: fix(desktop): do not double-speak auto-TTS replies**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#102960`
- **#102972: desktop: fix auto_tts double-read race in useAutoSpeakReplies**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#102970`, `#102960`

## Fix status

- No merged fix on record.