⭐ Get the Agent OS + join 3,400+ founders inside the AI Profit Boardroom → Join AIPB

GoldieBench Blog · 6 min read

Hermes Agent for iPhone: How to Reach Your Agent From iOS and a Test Plan for Each Route

Every route from an iPhone to your Hermes agent, and a repeatable set of tests to prove the one you pick.

Illustrated smartphone beside a benchmark checklist with pass marks on a dark navy background with gold accents

Hermes Agent for iPhone works through three routes, and a short test plan shows which one holds up for you.

The agent stays on your own computer or server; the phone reaches it through an app, Safari or a chat app.

Book a free SEO strategy session →

For the search side of your business, book a free SEO strategy session with Goldie Agency.

Route details follow the Hermes desktop docs and the messaging overview.

The routes

RoutePhone sideHost side
Client appIndependent App Store clientYour Hermes host, dashboard or Webapp
Web AccessSafariHermes desktop app with Web Access on
MessagingTelegram, iMessage or ntfyhermes gateway with that platform

Client apps found on 19 November

No app from Nous Research showed in a US App Store search.

Independent clients worth testing: Redde Agent for CarPlay, Hermes Conduit for Apple Watch, Hermex for the Webapp, plus HermesPilot, Hermes HQ and the Companion app.

Setup notes per route

Web Access: Settings then Web Access in the native desktop app, signed in with your Nous account; same-network address on port 9120 by default, or your own HTTPS front for remote use.

Telegram: Create with QR in the dashboard or desktop app, or a BotFather token; the Telegram page has both.

iMessage: BlueBubbles on an always-on Mac, or Photon with no Mac.

Test 1: reachability at home

On the same Wi-Fi, open the route and send "reply with the time".

Pass if the reply arrives and matches the host's clock.

Test 2: reachability away from home

Switch the phone to mobile data and repeat.

Pass for Telegram, Photon and an HTTPS-fronted Web Access or client; the plain HTTP Web Access option is not meant to pass this test.

Test 3: allowlist

Message the agent from an account that is not allowed.

Pass if it gets no answer, or a pairing prompt if you set that behaviour.

Test 4: voice memo

On Telegram, send a short voice memo with a clear task.

Pass if the agent transcribes it and restates the task correctly.

Test 5: session carry-over

Start a chat in a client app, then open the same session on desktop.

Book a free SEO strategy session →

Pass if it continues. Per the Webapp docs, a session opened by a phone client via the dashboard sign-in shows a mobile or ios label and behaves like any Desktop chat.

Test 6: scheduled delivery

Set a home channel and schedule a one-line report.

Pass if it lands on the phone at the set time.

Reading the results

ResultLikely causeFix
Test 2 fails on Web AccessUsing the plain HTTP same-network optionAdd an HTTPS front such as Tailscale Serve
Test 3 failsAllowlist openRestrict allowed users for that platform
Test 5 failsClient not using the dashboard loginCheck the app's connection settings
Test 6 failsNo home channel setRun sethome in the target chat

Does the model matter on mobile?

The route carries the messages; the model writes the replies.

GoldieBench scores models on building tasks, not on chat replies or transcription, so no score here would help you pick a phone model.

Judge models on test 4 and on how short and clear their phone replies are.

Test 7: profile mapping

If you run more than one Hermes profile, connect the phone to each in turn.

Pass if each route lands on the profile you expect, which you can check by asking the agent which profile it is.

Standalone profiles with their own gateway serve their Webapp on their own port, so a wrong port is the usual failure.

Test 8: relay uptime

For BlueBubbles, leave the Mac idle overnight and send a message in the morning.

Pass if it arrives without waking the Mac by hand; fail means power settings need changing.

For Photon, send from two different contacts on the free tier and check each conversation stays on its own line.

Test 9: attachment from the phone

Send a photo or a PDF from the phone and ask for a one-line description.

Pass if the agent reads the file, which proves the route carries attachments, not just text.

Book a free SEO strategy session →

Test 11: low signal

Send a request with one bar of signal, then move to a better spot.

Pass if the request goes through once and does not arrive twice.

Test conditions to hold steady

Use the same host, model and request wording for every route you compare.

Test at a quiet time of day so a busy host does not skew the timings.

Keep a log template with the same columns for every run.

Test 10: stop switch

From the phone, ask the agent to stop the current task mid-way.

Pass if it stops and confirms, because you need a way to halt a job when you are away from the host.

If your route cannot do this, note the fallback, such as stopping the gateway from a second device.

Testing a client app before you trust it

Before signing in, read the listing's description and confirm it mentions connecting to your own Hermes host.

After signing in, check it shows the same sessions you see on desktop.

Log out and back in once to make sure it does not lose your host details.

Timing replies properly

Note the time you send each test and the time the answer lands.

Run the same request three times and take the middle result, since one slow reply proves little.

Compare Telegram and a client app on the same request; any gap points at the route rather than the model.

What a clean result looks like

Replies land at home and on mobile data, strangers get nothing, voice memos come back restated, sessions carry across, and the briefing arrives on time.

That baseline makes any later problem easy to spot.

Comparing routes with the same tests

Run tests 1 to 6 on two routes, such as Telegram and a client app, and write the results side by side.

The route that passes more tests with less effort is the one to keep as your main channel.

Keep the other as a fallback for when the first is down.

Safety checks to repeat

Confirm the Webapp port is never forwarded from your router.

Rotate a Telegram bot token with /revoke if it is ever shared.

Rerun tests 2, 3 and 5 after every Hermes or app update.

Notes to keep

Log the route, the app version, the Hermes version and each result.

The Hermes repo and the AI Profit Boardroom cover the next builds.

Book a free SEO strategy session →

Run the six tests on the route you pick, log them, and repeat after updates.

Then book a free SEO strategy session with Goldie Agency, and keep this test plan for Hermes Agent for iPhone.

FAQ

How do I test Hermes Agent for iPhone?

Check reachability at home and on mobile data, the allowlist, voice memos, session carry-over between phone and desktop, and scheduled delivery.

Why does Web Access fail away from home?

The same-network option is plain HTTP for trusted networks. Remote use needs your own HTTPS front such as Tailscale Serve.

Which model is best for phone replies?

GoldieBench does not test chat replies, so compare models on your own short phone requests.

Do iPhone client apps keep my history?

Chats a phone app starts through the dashboard login carry on like Desktop chats, labelled mobile or ios.

The same stack Julian uses

Run this stack yourself.

Every demo on this bench was built inside the Agent Operating System — one prompt, one shot, single HTML file out. The Agent OS, the prompts, the templates, the weekly walkthroughs and 3,400+ founders shipping with it every day all live inside the AI Profit Boardroom.

3,400+founders
258documented wins
38countries
4coaching calls a week