Getting Hermes onto your phone involves two separate steps: admission to the mobile beta and a connection to a running agent. An invitation handles the first part. You still need the Hermes environment that will carry out your work.
Start with the official waitlist
As of November 7, 2026, the official mobile page directs visitors to select a platform and join the beta waitlist. Registration therefore does not mean immediate access.
Reports in the official repository describe an Android testing group reaching capacity and an earlier iOS invitation failing to open. Those are user reports about previous invitations. The current entry point is the official waitlist.
Connect to the machine doing the work
Prepare Hermes on your computer or server and connect a model provider first. The official documentation explains desktop and command-line installation. Managed cloud hosting through Nous Portal is another option.
An iOS mobile issue documents two connection paths: Gateway address connects to the running backend’s address, while SSH & Mosh provides a route into a remote machine. SSH is a protocol for encrypted access to another computer. The phone is your access surface; the connected machine runs the agent.
For a first check, connect to your running installation and request a small draft. Establishing that connection before delegating a longer job makes it easier to identify which step needs attention.
Separate free software from running costs
The official FAQ says Hermes is free software under the MIT license. Model providers and optional hosting can charge separately. Account for those costs when considering mobile access.
Hermes retains conversations, memories and skills. Stopping a local agent process preserves those records, but tasks requiring an active agent cannot run while it is stopped. If you want to assign work while away, the connected machine needs to remain available.
Check the connection path before changing passwords
In an iOS report filed November 1, the app displayed a credentials error even though SSH and dashboard authentication succeeded on the server. The reporter connected using Gateway address over a private Tailscale network. For a similar symptom, compare the connection route with server logs before assuming the password is wrong.
The security documentation treats user authorization and human approval of dangerous commands as separate controls. Preserve both while troubleshooting. The useful handoff is remote access with clear decision points: a convenient phone connection should help you supervise the work you delegate.
