Hermes Agent on Android Web Dashboard Guide
Android APK → Hermes Agent on Android → your browser opens the Web Dashboard for control. This guide walks through every dashboard page, configuration step, and feature — from first launch to a fully operational AI agent on your phone.
Access Methods
Method A — Local Access
Open http://127.0.0.1:9119 directly in the phone's browser. No login required. Fastest way to get started.
Method B — Remote Access
Use the phone's local network IP — e.g. http://192.168.x.x:9119 — to access the dashboard from a computer or other device on the same network.
Dashboard Pages Overview
Four functional groups across 13 pages:
Core
- Status — Agent health, auto-refreshes every 5s
- Chat — Full terminal in browser; slash commands
- Config — 150+ settings via form editor
- API Keys — Manage .env keys; /reload to apply
Management
- Sessions — History with full-text search
- Logs — Filterable agent/gateway logs
- Analytics — Token usage and cost stats
- Profiles — Isolated instances
Automation
- Cron — Scheduled tasks, visual builder
- Skills — Browse and install from Hub
- MCP — Server management, one-click install
- Webhooks — Subscriptions
System
- Channels — Configure Telegram, WhatsApp, Discord, Slack, WeChat, Lark and more
- Pairing — Approve user access requests
- System — Updates, backups, diagnostics
Configuration & Minimal Setup
Connecting a channel — Go to Channels → select a platform → enter credentials → test → restart the gateway. Or just tell the Agent in Chat: "generate a QR code to connect Telegram."
Minimal working flow:
- Open 127.0.0.1:9119 on the phone
- Confirm health on Status; test Chat
- Enable Channels → Cron → Skills
- Turn on Checkpoints in System
Messaging Platform Setup
Hermes connects to the chat apps you already use — Telegram, WhatsApp, Discord, Slack, WeChat, and Lark are all supported as channels.
Generate QR / Token
Scan / Authorize
Confirm & Test
Approve Users
Two layers control access: Channels configures the platform; Pairing controls who can talk to the bot. Use DM pairing (recommended) for flexible one-time codes, or a static allowlist for fixed user IDs.
Inbound Test
DM the bot — it should reply instantly.
Outbound Test
Run a multi-step task; confirm the streaming indicator.
Delivery Test
Trigger a Cron task; confirm the result lands in the right chat.
Cron Scheduled Tasks
Method A — Natural Language (recommended): Say in Chat: "Every day at 9am, summarize Hacker News AI news and send it to Telegram." The Agent translates intent into a cron expression automatically.
Method B — Cron Page Form: Manually set name, prompt, cron expression, and delivery target. Use Method A first, then fine-tune here.
Putting It All Together
- Cron Trigger — Scheduled at 8am daily
- Weather Tool — Agent calls a weather lookup
- Delivery — Result sent via the configured channel
Set up Channels first, then build Cron tasks — the delivery target must already be online. Layer features one at a time for a stable setup.
Advanced Configuration & Troubleshooting
To ensure maximum uptime and performance for Hermes Agent on Android devices, keep these operational considerations in mind:
Battery Optimization
Disable aggressive OS battery saver rules for the APK so the background service isn't killed while idling.
Port Management
By default, the Web Dashboard runs on port 9119. If port conflict occurs, adjust it via the Config page or directly in .env.
Guide Hermes Agent on Android to Automatically Configure SSH Service (PRoot Environment)
Instead of manually typing commands line by line, you can send the following prompt directly to Hermes Agent on Android, allowing it to configure and launch the SSH service properly inside the PRoot container environment.
Copy and send the following prompt to your Hermes Agent on Android:
Please configure and start the SSH service in the current PRoot Linux container environment according to the following requirements: 1. Install OpenSSH Server apt-get update && apt-get install -y openssh-server 2. Create required directory mkdir -p /var/run/sshd 3. Set root password echo 'root:123456' | chpasswd 4. Modify sshd_config settings # Allow root login sed -i 's/^#PermitRootLogin.*/PermitRootLogin yes/' /etc/ssh/sshd_config # Enable password authentication sed -i 's/^#PasswordAuthentication.*/PasswordAuthentication yes/' /etc/ssh/sshd_config # Disable PAM (Required in PRoot environment) sed -i 's/^UsePAM yes/UsePAM no/' /etc/ssh/sshd_config # Change port to 2222 (Non-root Android apps cannot bind ports < 1024) sed -i 's/^#Port 22/Port 2222/' /etc/ssh/sshd_config 5. Verify configuration sshd -t 6. Start SSH service /usr/sbin/sshd -D -p 2222 & 7. Verify service process ps aux | grep '[s]sh[d]' Final Configuration: • Port: 2222 • User: root • Password: 123456 • PAM: Disabled • Password Authentication: Enabled Connection Command: ssh root@<Device-IP> -p 2222 Why this is done: 1. Disable PAM - PRoot cannot write to the Linux audit subsystem loginuid, which causes PAM modules to crash. 2. Non-standard port - Non-root Android applications cannot bind to ports below 1024. 3. Allow root login - Simplifies configuration for easier debugging. 4. Create /var/run/sshd - sshd requires this directory to store its PID file.