“Couldn’t reach the address”
Check that hermes serve is running. On the computer, curl http://127.0.0.1:9119/api/health should answer. Then make sure the phone and computer are on the same network or the same tailnet, and that the address in Herald matches how the phone reaches the computer.
Signed out, or stuck on 401
Your dashboard password changed or the session expired. Herald signs in again on its own when it has the password saved. Otherwise open Settings › Connections, tap the connection and enter the password, or run npx herald-setup again and rescan.
My bot list is empty
The default profile’s gateway may be stopped while your bots run under another profile. Start the gateway for that profile, or pair Herald with a hermes serve scoped to it.
Push notifications never arrive
Push needs three things: the hermes-bot-push plugin on your computer, a real phone (simulators can’t receive push), and a tap on Register while connected. Use Send a test push to check the phone side, then check the plugin log on the computer.
Creating a bot with a custom model fails
A new bot starts from your default profile’s model. A model from a custom provider works when that provider is also behind your default model. Otherwise pick a built-in provider model or Use Hermes default, or add the provider to the new profile’s config.yaml by hand.
A screen crashed
The recovery screen has a Copy error button. Paste the result into the support form along with your device and Herald version, and we’ll take it from there.