How to Use Hermes Agent on Your Phone (2026)
Six real ways to run and control Hermes Agent from a phone in 2026: Telegram, Hermex, Onepilot, hermes-webui mobile, Termux, and hermes-android.
The Short Answer
Yes, you can run Hermes Agent from your phone. As of 2026 there is no single official native mobile client published by Nous Research, but the community has already built the pieces: a native iPhone app, an iOS SSH IDE that installs and drives Hermes remotely, a mobile-first browser UI, a Termux path that runs the agent on the device itself, an Android control plane that lets Hermes drive your phone, and the easiest option of all, using Telegram or Signal as the front door to a Hermes runtime living on a small VPS.
This post walks through all six paths, what each is really good at, and where the sharp edges are. If you just want the recommendation up front: for most people the messenger path is the one that survives daily use, and the native iPhone client is worth installing on top of it if you use hermes-webui.
Path 1: Any Messenger, Any Phone (The Easiest)
Hermes ships first-class integrations with Telegram, Discord, and Signal, and community skills add Slack and WhatsApp on top. When Hermes runs on a VPS or a home box, you already have a phone client: the messenger app you use every day.
- Latency: sub-second to the runtime once the agent is warm.
- Battery cost: zero. The agent runs on the server, your phone just talks to it.
- Setup on your phone: none, beyond having the messenger installed.
For the details of the messenger wiring, our Telegram deployment guide, the Signal walkthrough, and the Slack setup each cover the exact steps. All three surface the same runtime, so once Hermes is up, you can bridge to whichever one you actually message from.
The reason this path is the default for so many self-hosters is honesty about where mobile phones fail: they suspend background jobs, they change networks, they run out of battery. A messenger front-end sidesteps every one of those constraints because the agent is not the phone. Your phone is a dumb terminal onto a machine that never sleeps.
Path 2: Hermex, the Native iOS Client for hermes-webui
If you run hermes-webui as your control surface, there is now a proper native iPhone client for it. Hermex is a SwiftUI app built by an indie developer, launched in June 2026, currently free on the App Store with no in-app purchases and no analytics. Under the hood it just talks to your hermes-webui server's REST and WebSocket API over HTTPS or a Tailscale hop, so no data is proxied through a third party.
What it gives you that the messenger path does not:
- Session management: switch between conversations without ambient noise.
- File and photo attachments straight from the iOS share sheet.
- Workspace file browsing, so you can peek at what the agent is reading.
- Model, profile, and reasoning-effort controls in the composer footer.
- Skills, memory, and usage panes as first-class views.
If you are already committed to hermes-webui on a home server or a small VPS, Hermex is a low-cost quality upgrade. Requires iOS 18 or later.
Path 3: Onepilot, the iOS SSH IDE That Installs Hermes For You
Onepilot takes a different angle. Rather than talk to a running Hermes over HTTP, it opens a real SSH tunnel from your iPhone, installs the Hermes CLI under nvm with no sudo, wires up your model provider and messenger channel, and then wraps the running agent with a terminal, a file browser, git tools, and cron.
For people who already live in terminals, this is the closest thing to a mobile DevOps cockpit for Hermes. You get the full agent runtime, a syntax-highlighted view of the files it is editing, and the ability to inspect skills the agent has invented and either promote, demote, or delete them. The install is reversible: rm -rf ~/.nvm ~/.hermes on the host cleans it up.
The tradeoff is that Onepilot is a more ambitious app. It requires iOS 18.6 or later, and you are handing SSH access on your phone to a third-party binary. Read the permission model before you point it at production infra.
Path 4: hermes-webui in a Mobile Browser
Before there was Hermex, the community's mobile answer was to run hermes-webui and open it in Safari or Chrome on the phone. That path still works and is worth mentioning because it needs no App Store install.
hermes-webui is a single-Python-file, no-build-step SPA that ships a responsive three-panel layout: sessions on the left, chat in the middle, workspace files on the right. On a phone the panels collapse into a swipeable stack, and a viewport fix landed early on to handle the iOS URL bar cleanly.
If you are already exposing hermes-webui on a domain behind Tailscale or an HTTPS reverse proxy, add it to your home screen and you have a decent PWA-style client with no build pipeline of your own. It is not as smooth as Hermex, but it works cross-platform, including Android.
Path 5: Hermes On the Phone Itself (Termux, Android)
If you want the runtime to live on the device, Android via Termux is currently the only serious path. Nous Research documents a Termux install directly, and the Hermes-Agent-On-Android community project ships a one-liner installer that handles the pkg dependencies, creates the venv, and links hermes onto the Termux PATH.
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
The honest tradeoffs:
- Voice mode is currently blocked by
faster-whisperdependencies on Android. - Browser and Playwright auto-bootstrap is skipped, so browser-driving skills need manual work.
- Docker-based terminal isolation is not available, so sandboxed shell tools degrade.
- Android suspends Termux background jobs aggressively; keeping the agent alive across screen-off requires the standard Termux battery-optimization exemptions.
For a hacker who wants Hermes literally on the phone, this is the path. For a daily driver where you just want to chat with the agent, Path 1 or Path 2 will hurt less.
Path 6: Hermes Uses Your Phone (hermes-android)
The last path inverts the direction. Hermes still runs on a server, but a companion Android app (the hermes-android control plane) exposes phone capabilities such as SMS, calls, and calendar to the agent as tools. Now Hermes can use your phone, not just be reached from it.
This is a niche path but powerful for automation: draft a reply to a text and have it actually send from your number, or read a calendar event and cross-reference it against a memory the agent has been keeping. Setup is closer to a home-lab project than an App Store install, and you should treat the tool permissions with the same care you would give any script that has access to your SIM.
Which Path to Pick
A quick decision matrix:
| You want to... | Pick |
|---|---|
| Chat with the agent from your phone with zero setup | Path 1 (Telegram / Signal / Discord) |
A polished native iPhone app on top of hermes-webui |
Path 2 (Hermex) |
| Full SSH DevOps cockpit for Hermes from iOS | Path 3 (Onepilot) |
| A cross-platform mobile client with no app install | Path 4 (hermes-webui PWA) |
| Hermes to actually run on the device | Path 5 (Android + Termux) |
| Hermes to be able to send SMS or read your calendar | Path 6 (hermes-android) |
None of these are exclusive. The most common healthy setup is Path 1 as the daily driver, plus Path 2 or Path 4 for when you want the visual session view.
If You Do Not Want to Touch a VPS at All
Every path above assumes you can host Hermes somewhere. If the answer is no, and you just want a personal Hermes Agent on your phone, Hermify is the no-host route: a managed Hermes Agent on Telegram, live in about a minute, with memory that stays yours. You bring your model key or use a managed one, and your phone is the interface via Telegram, same as Path 1. No VPS, no signal-cli, no Termux battery tricks.
For a self-hosted-versus-managed comparison, our hosting vs self-hosting breakdown covers the tradeoffs in more detail.
Sources
Run Your Own Hermes Agent
Bring your API key, connect Telegram, and get a self-improving AI agent live in 60 seconds.
Get Started