.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
The Hermes agent finally has a mobile app. It's called Hermex, it's free on the App Store and as of yesterday the entire codebase sits on GitHub under an MIT license. iOS only for now, and I'll get to what that means further down, because I don't think it stays that way for long.
So, the whole point of Hermes is a server that never sleeps: persistent memory, scheduled jobs, self-written skills and everything else the agent learns depend on a machine staying online. Steering it from a phone has been the weak spot. You could bridge it into Telegram or open the web UI in Safari and squint at desktop layouts. I've done both. Neither feels like an app, and neither survives a spotty connection on the metro.
What is Hermex
Hermex is a native SwiftUI client built by indie developer Uzair Ansar for hermes-webui, the open source web interface and API server for Hermes Agent, now past 14,000 GitHub stars. The listing appears on the App Store as Hermes Agent Mobile, and the model is refreshingly clean: the agent and all your data stay on hardware you control, and the phone becomes the remote. No middleman service and no account with anyone.
It launched quietly in June 2026 and currently holds a 4.7 rating. Free with no subscription and no in-app purchases. It needs iOS 18 or newer and it's a real native app, no webview wrapper, which you can now verify yourself since the Swift source is public.
Hermex features
The headline feature is live streaming chat. You watch responses arrive token by token, including the collapsible thinking blocks and tool-call cards you'd see in the web UI, and you can steer a run mid-flight or stop it outright. The composer supports file and image attachments, plus per-message control over model, reasoning effort, workspace and profile.
Around the chat sits the rest of the cockpit. Every session on your server is browsable and searchable from the app, and recently viewed conversations stay readable offline through a local cache (seven days or 5,000 messages, clearable anytime). A model picker with recents and favorites covers every provider your server is configured for. There's a Tasks screen for viewing and editing the agent's cron jobs, a searchable list of installed skills, a file browser for the server's workspace and read-only panels for agent memory and usage insights. The repo also ships a share extension and a Live Activity widget, so a long-running job can sit on your lock screen while you do something else.
The read-only parts are deliberate, by the way, and I respect the choice. The project docs state plainly that dangerous write and admin surfaces stay off the phone until the mobile UX for them is explicit and safe. An agent with shell access deserves that kind of caution.
My favorite detail is the onboarding. Instead of walking you through server commands, the app generates a setup prompt you paste to your own Hermes agent. The agent then installs hermes-webui on its own machine and handles the password and remote access setup by itself. Using the agent to provision its own mobile remote is very 2026, and it works.
Hermes Agent, hermes-webui and Hermex
Three layers, each a separate open source project, and the names confuse people so let me untangle them once. At the bottom runs Hermes Agent itself, the self-hosted assistant from Nous Research with persistent memory and self-improving skills. On top of it sits hermes-webui, a Python server (with a vanilla JS frontend) that exposes the agent on port 8787 with near 1:1 CLI parity. Hermex is the third layer, a mobile client speaking to that API and nothing else.
The developer is unusually disciplined about that boundary. The app is tested against a pinned upstream commit, decodes server responses tolerantly so unknown fields never crash it, and documents openly that hermes-webui doesn't guarantee API stability yet. Practical translation: keep your server reasonably current, and mention your server version if you file a bug.
Hermex setup with Tailscale or Cloudflare Tunnel
You bring your own server. Hermex ships no backend, which is exactly what you want from a privacy standpoint. The flow splits into a server half and a phone half, and the whole thing took me well under half an hour.
On the server, run hermes-webui on a machine you control (Python 3.11+ on Linux or macOS; Windows works through WSL2), set a password via the HERMES_WEBUI_PASSWORD environment variable and make the whole thing reachable from outside. Cloudflare Tunnel gives you real HTTPS without opening a port, and Tailscale keeps everything on a private WireGuard network instead; the app accepts plain HTTP only for Tailscale's device range, so there's no way to accidentally send your password unencrypted over the open internet. On the phone, enter the server URL and password. Done.
We've covered both access patterns in depth already: our Hermes Web UI remote access tutorial walks through the exposure options and our Tailscale guide for Hermes on a VPS covers the private-network route end to end.
Privacy and security
This is where Hermex earns the self-hosting crowd's trust. There are no analytics, no ads, no tracking and no third-party relay. Your messages travel between your phone and your server, nowhere else. The server URL lives in the iOS Keychain, the password is used to sign in and then discarded, and the offline cache sits on your device under your control. Claims like these usually require faith. Here they don't, because you can read the source line by line.
Hermex went open source yesterday
The announcement landed on the r/hermesagent subreddit on July 2 and the repo confirms it: full app source, MIT licensed, with contribution guidelines, contract tests, a code of conduct and even the working agreements the developer's coding agents follow. Anyone with Xcode 26 and an iOS 18 device can build it themselves, though the App Store build stays the recommended path unless you're developing.
The repo sits at a few dozen stars as I write this, which says more about the release being a day old than about the app. The web UI it drives took months to reach 14,000. Given how active the Hermes community is, I expect the client to pick up contributors fast, and the codebase reads like it was prepared for exactly that.
Android and iPad versions
Straight answer: iPhone today. An iPad version is listed as coming soon on the official site, so that one is a matter of time.
Android is my speculation, clearly labeled as such, but I'd put money on it. The hard problems (the API contract, the auth model, the session semantics) are already solved and documented in a public repo, so an Android client only needs to speak the same hermes-webui API. Open sourcing the iOS app hands any Kotlin developer a working reference implementation. In a community this active, someone picks that up. Until then, Android users still have the web UI itself, which works fine in a mobile browser even if it can't match a native app.
Run Hermes Agent on a VPS
A mobile remote is only useful when there's something awake to remote into. A laptop that sleeps when you close the lid breaks the whole promise, so the natural pairing for Hermex is a small always-on server. Our Hermes Agent VPS comes with the agent preinstalled and keeps it online on NVMe storage, and adding hermes-webui on top takes one bootstrap command.
From there the combination gets genuinely fun. Cron jobs you scheduled from your phone fire while you sleep. A research task you started at your desk streams to your lock screen on the tram. If you're new to the agent itself, start with our complete Hermes Agent guide and work up to the mobile layer from there.
Hermes finally fits in a pocket. It took an indie developer and a healthy refusal to put anyone's cloud between you and your own agent.
