Hermes in your pocket

There are two genuinely different answers here and people conflate them. Either the agent runs on a server and your phone is a client, or the agent runs on the phone. The server-plus-client path is what almost everyone ends up on, so start with hermes-webui and only reach for a native client if the web view specifically annoys you. Pick the messaging bridge based on where you already live — Telegram dominates the corpus, but the same shape works elsewhere. The on-device install is a real option, not a toy, but it is a different set of tradeoffs around battery, background execution and model cost.

Real posts from the Hermes community, mirrored from Nous Research's user stories corpus.

• Exposing a self-hosted agent to the internet for phone access is the most common way people accidentally publish a shell. Tunnel it (Tailscale or equivalent) rather than opening a port.
• Native mobile clients pair with a specific backend — check the pairing requirement before assuming any client works with your setup.