Troubleshooting

1. Check that the dashboard service is running on the computer:

macOS:

launchctl print gui/$(id -u)/com.hermes.shared-dashboard

Linux:

systemctl --user status hermes-mobile-dashboard

Windows: open Task Scheduler and look for the task Hermes Mobile Dashboard. It should be Running.

2. Check Tailscale (if you use it): both the computer and the phone must be signed in to the same Tailscale account, and Tailscale must be switched on in the phone's app.

3. Pair again. Re-run the installer with --pair (Windows: HERMES_MOBILE_PAIR=1) and scan the new code.

The password the app has saved no longer matches the dashboard, usually because the installer was re-run or the password was changed. Pair again: re-run the installer with --pair and scan the QR code.

Grant Full Disk Access to Hermes.app: System Settings → Privacy & Security → Full Disk Access → + → your home folder → Applications → Hermes. See step 2 of the setup guide.

Already did that? After a Hermes update that ships a new Python, macOS may treat it as a different app. Remove Hermes from the Full Disk Access list and add it again.

That prompt comes from the 1Password desktop app integration, which needs someone at the computer. Use a service account instead, which works headless:

• Re-run the installer with --onepassword and paste a service-account token.
• Service accounts can't read the built-in Personal (or Private) vault. Move the items your bots need into a dedicated vault and give the service account access to it.
• Optionally, turn off Integrate with 1Password CLI in the 1Password app's Developer settings so the prompt can't appear at all.

Google rejects headless browsers at the OAuth hand-off. Re-run the installer with --real-browser <bot> so that bot uses a visible, real Chrome with a copy of your profile.

Keep your regular Chrome closed on that computer while the bot is browsing.

• Check that the hermes-mobile plugin is installed: re-run the installer.
• Restart the dashboard service (see the first question for where to find it).
• The bot's browser must run locally on your computer. Screen share doesn't work with cloud browser providers.

Make sure ELEVENLABS_API_KEY is set in ~/.hermes/.env and that the key is valid, then re-run the installer with --voice. Also check the phone isn't on silent and that a voice is chosen for the bot in the app.

• Turn them on in the app under Settings → Notifications, and allow notifications for Hermes Mobile in the phone's settings.
• The relay must be running on the computer. If you installed with --no-push, re-run the installer without it.