People searching for a phone or mobile Hermes Agent workflow usually do not want another terminal tutorial. They want to start a job from a train, check a cron report from bed, reply to a Telegram bot, or see whether an agent finished without SSHing into a server.
Quick answer#
There are four practical ways to use Hermes Agent from your phone. Use Telegram or Discord when you want a chat interface, use the Hermes Agent dashboard / Web UI when you need browser Chat and private operator visibility, use a community Android/iOS-style client only when you are comfortable securing your own server, and use FlyHermes when the real goal is managed browser/mobile access without operating the host and gateway; check the plan for model access, allowances and any credentials you still supply.
Start with the first useful Hermes setup workflow on the machine that owns the runtime. Only after the local turn works should you add a phone surface and test one real reply. This keeps “use Hermes from my phone” separate from the harder question of where Hermes keeps running when the laptop sleeps.
Do not expose the self-hosted dashboard as a public mobile app just because it opens in a browser. The dashboard is an admin surface. If you need mobile access outside your network, put it behind SSH tunnel, VPN, authenticated HTTPS, or choose the managed cloud path.
Closing the phone app does not close the hosting bill#
Your phone controls a backend; it does not determine that backend's billing state. Before a short mobile pilot, record which service owns the agent and where its usage balance or infrastructure invoice is shown. After leaving the app, inspect the backend through that service's controls rather than assuming the runtime stopped with the screen.
For example, the Nous Cloud FAQ, checked October 26, 2026, says a stopped agent still incurs storage charges and keeps its workspace. Running compute and inference/tool usage have separate meters. That rule belongs to Nous Cloud, not every self-hosted VPS or FlyHermes plan. FlyHermes's current offer instead describes a subscription with an AI-credit allowance.
If your goal is occasional phone access, compare both the recurring commitment and what happens between sessions using the Hermes cost worksheet. Do not cancel or delete the owning workspace until needed files are protected. A lost phone connection, a stopped agent and a canceled subscription are three different events.
Remove phone access without confusing three identities#
Losing access to a phone can involve a messaging identity, a dashboard browser session or a compromised bot credential. Identify which one is affected before making changes. The Dashboard Pairing page can revoke an approved messaging user; clearing pending requests is a different action. The Channels page can disable a channel but retains its token on disk.
Use the appropriate account or identity-provider recovery path for a compromised browser login, and the credential issuer for a leaked bot token. Do not rely on closing the phone tab or disabling a channel to revoke every identity. After recovery, verify the old access is rejected and a permitted client can complete one harmless task. Keep a trusted second access path so you are not locked out while repairing the phone. The dashboard guide covers the self-hosted operating boundary.
A phone reconnect is not the same as a backend restart#
The official TUI recovery reference distinguishes losing a connection from losing its process. For an attached dashboard gateway, a socket-only interruption can reconnect to the same session, including a reply still streaming on the backend, without resubmitting it. When a spawned gateway dies, reopening saved history does not recover the reply that was in flight. That distinction matters when a phone returns from sleep: the familiar conversation is not proof that the server stayed alive.
If selecting the old conversation instead shows “This chat is open in another Hermes window”, check the dashboard session-ownership diagnosis rather than repeatedly starting New chat. Record whether you merely hid the tab, closed it, lost the network or restarted the backend. Before retrying consequential work, inspect its actual destination. These are documented recovery boundaries checked October 19, 2026, not measured guarantees for your phone or hosting provider.
Closing a phone tab is not the same as hiding it#
The reconnect procedure below applies to an interrupted connection or a hidden tab. Closing the self-hosted Chat tab is a different event: current official Dashboard docs say its PTY is reaped on the server and reopening starts a fresh session. Saved history and a still-running command are not the same thing.
Before leaving a consequential task, note its profile, session ID and expected output. If you closed the tab, open Sessions on the owning profile and deliberately resume the old conversation rather than assuming the newly opened Chat is the same session. Inspect the result where it lives. Do not repeat a send, purchase or deployment just because the phone did not display a final answer.
For work that must continue with the browser closed, use a separately supported background workflow and test it first with a harmless artifact. Mobile operating systems can suspend clients; do not infer server-side continuity from a familiar tab title. The dashboard handoff checks cover the self-hosted boundary. Choose FlyHermes managed access for less host maintenance, while still checking the product's supported task and background-run behavior.
A new chat and a resumed chat can use different folders#
Current official Dashboard documentation describes a workspace selector in the embedded TUI Chat rail. This matters when you open your private dashboard from a phone: the directory where the dashboard process started is not necessarily the project you want the agent to work on.
Select the owning profile, choose the intended workspace and start a New chat. The choice applies to the next new session; resuming an existing conversation keeps that session's working directory. On narrow screens the rail folds into a slide-over panel. If a just-cloned project is absent, rescan the host's workspace list rather than creating a second profile. A missing path should be investigated on the backend, not on the phone.
Before permitting edits, ask the agent to report its working directory and confirm one harmless project filename without changing anything. Do not use a customer's private document as the canary. Repeat that check after switching profiles or backends; a familiar conversation title does not identify the machine holding its files.
These controls belong to the self-hosted dashboard's terminal-backed Chat, not a claim about FlyHermes's UI. Use the self-hosted versus managed comparison when your goal is phone access without operating the host. A managed workspace still needs the correct accounts and files connected.
Option 1: Telegram as the simplest phone client#
Telegram is usually the fastest mobile path because Hermes already supports a gateway pattern. The setup is still operational: bot token, allowed chats, gateway process, provider credentials, logs, and one real reply test. Start with the Telegram setup walkthrough or the step-by-step connect Telegram to Hermes guide.
Use Telegram when:
- You want a private DM-style mobile interface.
- You want voice-message transcription, quick status checks, and lightweight commands.
- You can keep a Hermes gateway process running somewhere reliable.
Avoid treating Telegram as solved until you have sent a real message from the exact DM, group, or topic that should work. A dashboard that says the gateway is configured is useful evidence, but the mobile phone test is the proof.
Option 2: Discord for team mobile workflows#
Discord is better when the agent belongs in a team room. A recent YouTube setup guide showed teams using Discord channels as a shared place where humans and multiple agents coordinate work. Hermes has dedicated Discord pages for both the integration overview and setup path: Hermes Agent Discord setup, Discord integration, and connect Discord to Hermes.
Use Discord when:
- The mobile workflow is team visibility, not just one private user.
- You want topic/channel separation for different agents or projects.
- You need teammates to see agent updates without giving them shell access.
The operational catch is the same as Telegram: Discord is a gateway. You still need a running process, a healthy model provider, valid bot permissions, and enough logging to diagnose missed replies.
Option 3: browser Chat on your phone#
The self-hosted Hermes Web UI includes the real terminal TUI in its Chat tab through a PTY/WebSocket connection. It supports conversation history, tool-call cards and approval prompts as well as the dashboard's management pages. You do not need FlyHermes merely to chat in a browser.
Keep this admin surface behind a controlled access path. Prefer a private VPN or SSH tunnel; an internet-facing HTTPS deployment needs the documented OAuth/OIDC setup and restricted origin access. HTTPS encryption alone does not authenticate a visitor. Check that a signed-out visitor cannot read protected management data before using the URL from a phone.
Recover a disconnected phone tab without repeating the task#
A phone can hide or suspend the browser tab when you switch apps. Current official Chat documentation says automatic reconnects pause while the tab is hidden or another dashboard page is open, then resume when you return. The PTY connection sends a small keepalive every 20 seconds; that helps idle timeouts but cannot defeat a proxy's hard connection-lifetime limit.
- Return to Chat and let it reconnect. Confirm the backend, profile and session before typing.
- Read the latest history and inspect the expected result. If the job could send a message or change an external record, check that destination too.
- If the same session is unavailable, open Sessions under the owning profile and use its resume action. Do not create a fresh chat and blindly repeat the instruction.
- If the disconnect repeats, inspect the authenticated
/api/ptyWebSocket and matching host logs using the dashboard recovery guide. Remove cookies, tokens and personal data before sharing diagnostics.
A reconnect is not proof that a task failed or succeeded. For a safe first test, request only the actual working directory and one harmless filename, switch away, then return and check the same session. Do not use a payment, publication or production deployment as a connectivity test. This procedure follows current documentation; it is not a measured guarantee across mobile browsers and proxies.
Option 4: Android/community clients for local-first users#
Community mobile clients can be useful if you specifically want phone-native interaction with a self-hosted Hermes server. The Android release found in the latest Reddit scrape is a good signal: people want voice input, spoken replies, and local-network/Tailscale-style access to their agent.
Use a community client when:
- You want local-first access over Wi-Fi, Tailscale, or another private network.
- You understand that the client is only one layer; the server, auth, provider keys, gateway, and updates are still yours.
- You are comfortable reviewing the project and its network/security assumptions.
For most non-operator users, this is not the first mobile path. Start with Telegram, Discord, or managed cloud access before adding another client surface.
When FlyHermes is the better mobile answer#
If the reason you searched for mobile Hermes is “I do not want to babysit a server,” the answer is not to expose the self-hosted dashboard. Compare FlyHermes pricing and the self-hosted vs hosted AI agent guide.
FlyHermes is the better fit when you want:
- Browser/mobile access without maintaining the runtime.
- Connected channels without doing gateway uptime work.
- A documented plan for included model usage and any separately billed services. Verify those allowances before starting unattended work.
- A team-friendly path that does not depend on everyone knowing the CLI.
Self-hosting is still the right answer when you need full control, custom infrastructure, private networks, or local-only operation. The point is to choose intentionally instead of accidentally turning a dashboard into an insecure mobile app.
Phone-access checklist#
Before you call the mobile setup done, verify these five things:
- The CLI works:
hermes doctorand onehermes chat -qsmoke test pass. - The phone surface works: Telegram, Discord, dashboard tunnel, or mobile client receives a real reply.
- The provider route works under the same runtime: no hidden API-key, credit, or rate-limit mismatch. Use the provider costs and rate limits guide if replies fail under load.
- The runtime stays available: test the always-on host and gateway after a restart. A service manager cannot keep a sleeping laptop awake; use an always-on machine or managed hosting if jobs must continue after you close it.
- The security boundary is explicit: private chat allowlists, private dashboard access, VPN/Tailscale, or managed cloud.
FAQ#
Can I use Hermes Agent from my phone?#
Yes. The common paths are Telegram, Discord, a private dashboard/Web UI connection, community mobile clients, or FlyHermes managed cloud access. The right choice depends on whether you want chat, monitoring, team workflow, local-first control, or managed uptime.
Is the Hermes dashboard safe to open on my phone?#
It is safe only when the access path is private and controlled: localhost, SSH tunnel, VPN, private network, or authenticated HTTPS. Do not expose the raw dashboard port publicly.
Is Telegram or Discord better for mobile Hermes?#
Use Telegram for a simple personal phone bot. Use Discord when teammates, channels, forum topics, or multiple agents need shared visibility.
Is FlyHermes required for phone access?#
No. Self-hosted Hermes can be reached from phone-friendly clients, but FlyHermes is the simpler path when you want hosted browser/mobile access and managed uptime instead of maintaining the server and gateway stack yourself.
Phone access does not decide where Hermes runs#
Telegram, Discord, Slack, a private dashboard, and FlyHermes can all look like phone access, but they do not share the same ownership model. With a self-hosted channel or dashboard, your laptop, Docker host, or VPS still owns the runtime, files, secrets, provider keys, gateway process, backups, and recovery. FlyHermes is the managed option when the requirement is reliable browser/mobile access rather than operating that backend. Use the self-hosted vs hosted comparison before exposing a dashboard only to make Hermes reachable from a phone.
Browser reliability from a phone#
Phone access does not remove browser-session limits. For remote browser work, require a fresh-session check, screenshot, console result, and final artifact; a quiet channel or stale CDP URL is not proof of success. Use the Hermes browser automation troubleshooting guide for 502, Docker-localhost, CAPTCHA, and page-JavaScript failures.
Your phone is the control surface, not the runtime#
Telegram, Discord, WhatsApp, and a browser can control Hermes from a phone, but they do not keep a laptop-hosted agent running after that laptop sleeps. Put the runtime on an always-on machine or use FlyHermes, then prove one scheduled delivery with the phone and laptop clients closed. The self-hosted vs hosted comparison provides the ownership test.
Phone control does not move your Chrome identity to the phone#
A phone message can trigger a browser task, but local Chrome login state remains bound to the machine and Hermes profile running that task. If the workflow uses a real-profile snapshot, pin and test the intended identity on the host first. Use the browser troubleshooting guide for that setup, or choose FlyHermes when managed browser/mobile operation is the goal.
Telegram topics for parallel phone workflows#
For several phone-based workstreams, enable Telegram Threads and use /topic so each topic maps to a separate Hermes session. Pin scheduled output with TELEGRAM_CRON_THREAD_ID, and follow the current Telegram setup guide for group authorization, polling/webhooks, and restart-safe delivery.
A Desktop session token is not a phone-browser login#
Before moving a remote URL from Desktop to your phone, check the backend's authentication mode. The current official deployment-token documentation explicitly says token-only deployments have no browser sign-in flow. Desktop's Session token field is a client credential channel; opening the same address in Safari or Chrome does not provide that credential automatically. A login page with an explanatory note and no buttons is not necessarily a broken installation.
Do not add the secret to the address bar or share it in a mobile screenshot. For browser access, have the authorized operator configure a documented browser-login provider appropriate to the exposure: username/password on a trusted network or VPN, or Nous OAuth/OIDC for shared or internet-facing access. Preserve the existing private path until signed-out management requests are denied and the intended signed-in browser can open the correct profile and complete one harmless Chat exchange.
If you only need a phone conversation rather than administration, an already authorized messaging gateway may be the simpler surface. The dashboard decision guide and remote Desktop guide explain the boundary. Checked November 2, 2026; this is documented client-selection guidance, not a mobile authentication test we performed.