dilim/hermes-agent
1
0 Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-11-06 05:17:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(voice): the Webapp always relays voice

Browse Source
This commit is contained in:
IAvecilla authored and Teknium committed 2026-11-05 10:15:02 -08:00
1 parent 1e81ee57e3
commit 6b5f6ee269
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
website/docs/user-guide/features/voice-mode.md
+1 -1
View File
@@ -214,7 +214,7 @@ When Hermes Desktop is connected to a **remote gateway**, audio does not need to
There is nothing to configure on the client: the profile you're talking to is the single source of truth for providers and keys, exactly as if the gateway had done the work itself. Keys are held in the desktop's memory for the session only — never written to disk on the client.
Providers that can only run on the gateway host (local whisper, `edge` TTS, command providers, plugins) automatically fall back to the relay path (`/api/audio/transcribe` and the speech WebSocket), as does any older backend without the endpoint. To force the relay for every provider, set:
Providers that can only run on the gateway host (local whisper, `edge` TTS, command providers, plugins) automatically fall back to the relay path (`/api/audio/transcribe` and the speech WebSocket), as does any older backend without the endpoint. The Webapp (the desktop UI in a browser) always relays: a browser tab cannot call a provider that does not allow cross-origin requests (such as Nous-managed audio), and its keys stay on the host. To force the relay for every provider, set:
```yaml
voice: