Install Android
Use Google Play for the everyday app. Choose Sideload only for Device Control.
Start with the standard upstream Dashboard/Gateway connection. Then pair Relay when you want the additional tools and enhancements it provides.
Use Google Play for the everyday app. Choose Sideload only for Device Control.
Scan Connect mobile app. This adds the standard Dashboard/Gateway connection.
Scan Pair new device. This unlocks Relay capabilities with a separate grant.
Upstream first, Relay encouraged
Chat, sessions, Manage, sign-in, and standard voice use the unmodified Hermes Dashboard/Gateway. The Relay plugin is an encouraged extension for Terminal and TUI, notifications, desktop tools, Relay sessions, enhanced voice, optional Device Control, and media compatibility or metadata. Ordinary inbound files use current upstream Dashboard routes. When upstream Hermes provides a compatible surface, Hermes-Relay prefers it instead of duplicating it.
For most people, install the Google Play build. It updates automatically and includes the everyday Hermes experience plus Relay capabilities that do not require Android Device Control.
Choose the signed Sideload APK only when you also want Hermes to read and operate the phone screen. Compare the builds and verify the APK →
The Dashboard/Gateway must be running and reachable from the phone. This is all the server-side setup required for standard Chat, sessions, Manage, voice, and inbound files:
hermes dashboardIn Android Connect, choose Find Hermes on LAN. If discovery cannot find the host, choose Enter your Hermes address and enter the Dashboard URL you open in a browser, normally http://<host>:9119. Sign in when prompted.
This creates a complete standard connection with no plugin or Relay URL. If the Relay Dashboard page is already installed, its Connect mobile app action can instead provide the same tokenless Dashboard-address setup by QR; that QR does not pair Relay or contain a password, cookie, or API key.
For the recommended complete experience, install and start Relay on the Hermes host after the standard connection works:
hermes plugins install Codename-11/hermes-relay/plugin --enable
hermes relay doctor
hermes relay start --no-sslUse --no-ssl only on a trusted LAN or VPN. For away-from-home access, Tailscale is the recommended route. Refresh or restart the Dashboard/Gateway plugin catalog after installation; a Relay page should appear.
In the Web Dashboard's Relay page:
The QR is single-use and normally advertises the Dashboard-origin Relay ingress, plus any configured direct compatibility routes. It can carry LAN, Tailscale, and public candidates so the phone can choose the best reachable route. Pairing unlocks Terminal/TUI, notifications, Relay sessions, enhanced voice, desktop-tool handoff, media enhancements, and—on the Sideload build—Device Control.
You are ready when:
Open Chat and send a message. Pairing Relay is encouraged for the complete experience, but an unavailable Relay must not block upstream Chat, Manage, or standard voice.
On the Hermes host, run:
hermes pairThe command prints connection details, a scannable one-time QR, a PNG path, and a pasteable hermes-relay://pair?... invite. Scan the QR from Android. This is the same pairing contract used by the Web Dashboard.
hermes pair --register-code <code> command on the host, then tap Connect.Detailed Android setup and security notes → · Dashboard and Desktop plugin pairing → · Troubleshooting →
[?] Get Help · [!] Found a Bug? · [+] Get Started