TalkToHermes

What TalkToHermes does

TalkToHermes combines an iOS app with a per-user TalkToHermes Voice Bridge that connects the phone to a Hermes Agent. You hold to talk, follow the full conversation on screen, and handle live approval and cancellation flows. Credentials are kept in the Keychain, the interface is available in English and German, and app language and spoken language are chosen independently.

Speech recognition and synthesis run through configurable fallback chains. For recognition the README names Faster-Whisper on a GPU system, Wyoming Faster-Whisper, MLX-Whisper on an Apple Silicon Mac, or a local Hermes STT model. For synthesis it names local Piper as the last resort, Wyoming-Piper, and optional OmniVoice for cloned voices. Audio files stay on your infrastructure even when Hermes uses a cloud LLM, and only transcribed text and conversation context go to the model provider. With a local model provider such as Ollama the whole interaction stays local.

Key features

• Native SwiftUI push-to-talk client with full conversation history
• Ordered fallback chains for speech-to-text and text-to-speech providers
• Live approval and cancellation flows
• Keychain-backed credentials
• English and German interface with separate spoken-language setting
• Optional cloned voices through OmniVoice

When to use it

• Talking to a home-hosted Hermes agent from an iPhone
• Keeping voice audio on your own network while using a cloud LLM
• Approving or cancelling an agent action by voice session

Who it is for: iPhone and iPad users who run their own Hermes Agent and want a private voice interface.

How it fits with Hermes Agent

Built for Hermes Agent: the app talks to a Hermes instance through the TalkToHermes Voice Bridge.

Requirements: A configured Hermes Agent, the TalkToHermes Voice Bridge, at least one STT and one TTS provider, HTTPS access to the bridge, an iPhone or iPad on iOS 17+, and Xcode if building from source

Note: It is not standalone: it needs a configured Hermes Agent, the Voice Bridge, speech services and a private HTTPS endpoint.

FAQ