# NousResearch/hermes-agent · Fix voice input labeling in CLI speech-to-text

## Open now

- Nothing open on GitHub.

These issues and PRs address a bug where the CLI incorrectly marks typed messages as voice input, with fixes to restrict voice-related prefixes and behavior to messages that actually originate from speech-to-text.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 3 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.50`: 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

- #65827: CLI voice mode marks typed messages as voice input

## Prior & competing PRs

- **#11744: fix(cli): route voice reply behavior by input origin**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#65827`
- **#65925: fix(cli): only mark speech-to-text messages as voice input**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#11744`
- **#65961: fix: only prefix voice-transcribed messages with \[Voice input...\] prefix (#65827)**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#11744`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`