# NousResearch/hermes-agent · GPT-Live voice routing in Bot chats

## Open now

- Nothing open on GitHub.

These items address how GPT-Live voice sessions are routed in desktop Bot chats, specifically ensuring the Bot's own profile voice is used rather than another profile. The work involves fixes and a related salvage of a prior change.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #117636. Verify it addresses your case.
- **Recommended:** read PR #117636 (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: `resolved` · deciding PR(s): `pr-117636`. 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 `1.00`: 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

- #117401: Desktop Bot chats: GPT-Live voice sessions should use the Bot’s own profile voice

## Prior & competing PRs

- **#117636: fix(desktop): GPT-Live in a Bot chat uses the Bot's own profile voice (#117401, salvage #117424)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/src/app/chat/composer/hooks/use-voice-live-conversation.owner.test.tsx`, `apps/desktop/src/app/chat/composer/hooks/use-voice-live-conversation.ts`, `apps/desktop/src/lib/voice-live.routing.test.ts`, `apps/desktop/src/lib/voice-live.ts`
- **#117424: fix(desktop): route GPT-Live sessions through the Bot owner's profile**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `c7f2e76c50`, `#117636`

## Fix status

- Merged to main in PR #117636 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.