Hermes-Relay

Hermes-Relay is the native Android companion for the Hermes agent you run. Chat, talk hands-free, continue sessions, and manage models, keys, skills, profiles, and automations from your phone.

It is not a hosted AI service. Your Hermes agent stays on infrastructure you control, and the app talks only to instances you configure.

QUICK START

1. Start the Hermes Dashboard/Gateway on your computer or home server with hermes dashboard.
2. Install Hermes-Relay from Google Play.
3. For the recommended full setup, install the Hermes-Relay plugin on the host and refresh the Web Dashboard. A Relay page will appear.
4. Scan Connect mobile app from Android Connect. Then scan Pair new device from Android Settings > Connections.

The QR codes are separate on purpose. Connect mobile app adds the standard Dashboard/Gateway connection. Pair new device grants a time-limited Hermes-Relay session for the additional capabilities you approve.

Standard Hermes without the plugin is supported. Choose Find Hermes on LAN or enter the Dashboard address you open in a browser, normally http://:9119. Pair the Hermes-Relay plugin later when you want the full experience.

HOW IT WORKS

Chat, sessions, Manage, sign-in, and standard voice use the unmodified Hermes Dashboard/Gateway. The separate Hermes API server is an optional fallback for advanced or headless setups; it is not required for the normal Android connection.

The encouraged Hermes-Relay plugin adds Terminal/TUI, notifications, media handoff, enhanced voice, Relay sessions, desktop-tool handoff, and time-limited per-feature grants. When upstream Hermes provides a compatible capability, Hermes-Relay prefers it instead of duplicating it.

GOOGLE PLAY AND SIDELOAD

The Google Play build includes Chat, voice, sessions, Manage, profiles, notifications, media, and Terminal/TUI when the Hermes-Relay plugin is paired.

Google Play does not include Android Device Control. It cannot tap, type, swipe, send SMS, place calls, or access contacts or location. Optional Voice Overlay provides user-started voice controls over other apps, with microphone notification and Stop voice. Selecting Hermes as Android Digital Assistant can provide bounded screen text and a screenshot for an explicit unlocked assistant invocation; this context goes to your configured server and AI provider.

Device Control is available only in the signed Sideload build on this project's GitHub Releases. It requires the Sideload app, a paired Hermes-Relay plugin, explicit Android accessibility permission, and the app's safety controls.

FEATURES

- Streaming Chat with reasoning, markdown, tool progress, attachments, mid-turn steering, edit-and-resend, and searchable commands.
- Manage models and provider keys, edit profiles, and browse, install, or update skills through the Hermes Dashboard.
- Hands-free voice through your server's speech providers. Hermes-Relay pairing adds per-profile voices and an experimental realtime engine.
- Inspect connection readiness, routes, response timing, token usage, and stream health without exposing credentials.

SECURITY AND PRIVACY

- Dashboard sessions and Hermes-Relay tokens use encrypted Android storage.
- Cleartext is limited to trusted local-network setups. Use a VPN or HTTPS remotely.
- No telemetry, ads, tracking, or third-party analytics SDKs.
- Notification and microphone access are optional and user-controlled.
- App traffic goes only to servers you configure.

REQUIREMENTS

- Android 8.0 or later.
- A reachable Hermes Dashboard/Gateway.
- The Hermes-Relay plugin is encouraged for the complete experience but never blocks standard Hermes.
- Network access through a local network, VPN, or operator-managed internet route.

OPEN SOURCE

Hermes-Relay is MIT licensed. Source, setup guides, downloads, and issue tracking are on GitHub.

This community project is not affiliated with or endorsed by NousResearch.

Recent changes:
v1.18.1 - Reliable browser sign-in

Browser sign-in stays connected while you complete your provider's flow and return to Hermes-Relay. The sign-in notification ends when the attempt finishes or is canceled, and callback pages identify the selected provider.