Hermes Web Dashboard (localhost:9119)
Not everyone wants to live in a terminal. The Hermes web dashboard gives you a browser window onto your agent at http://127.0.0.1:9119: chat, settings, API keys, sessions, logs, cron jobs, skills, MCP servers and channels. It's the friendliest on-ramp for non-terminal users, and the fastest way to see what your agent is actually doing. This guide tours each panel and shows how to reach it safely from a remote server.
Run hermes dashboard. It starts a local web server on 127.0.0.1:9119 and opens your browser. Options: --port 8080, --no-open. If Hermes runs on a VPS, don't expose the port. Tunnel to it over SSH (covered below).
What each page does
- Status. Version, gateway state and resource warnings at a glance.
- Chat. Talk to the agent in the browser. Handy for testing a new skill before you connect Telegram or Discord.
- Config and API Keys. The same settings as
config.yamland.env, in a form. API keys are stored masked, and leaving a field blank keeps the existing value. - Sessions, Logs and Analytics. Search past conversations, filter agent and gateway logs, and see token and cost usage.
- Cron. Create, edit, pause and trigger scheduled jobs. Overdue jobs are flagged.
- Skills and MCP. Turn skills on or off, and install MCP servers from the catalog. The MCP page shows exactly what each entry runs (MCP guide).
- Channels and Pairing. Configure each messaging platform, then restart the gateway from the page. Approve or revoke DM pairing codes (who can talk to it).
- Profiles, Webhooks and System. Switch between profiles, manage webhook subscriptions, and view system details.
Kanban boards have their own dashboard view (hermes kanban). Memory is two small files, ~/.hermes/memories/MEMORY.md and USER.md; review and prune what the agent learned with /journey (memory guide).
Reach it safely from a remote server (SSH tunnel)
The dashboard reads and writes your .env file, which holds your API keys. On 127.0.0.1 it has no login: anyone who can reach the port controls your agent. To use it on a VPS, forward the port to your laptop over SSH:
# On your laptop:
ssh -N -L 9119:127.0.0.1:9119 you@your-server
# Then open in your local browser:
http://localhost:9119The tunnel makes the remote dashboard appear as if it's running locally, while the port stays closed to everyone else. Close the SSH session and the access goes away.
Binding to 0.0.0.0 (hermes dashboard --host 0.0.0.0) puts your agent's control panel on the network. Current versions refuse to start on a public address until you configure a login: username and password (HERMES_DASHBOARD_BASIC_AUTH_USERNAME, …_PASSWORD, …_SECRET in .env) or OAuth. The old --insecure flag no longer turns that off. You need this setup to connect Hermes Desktop to a remote server. Even with a login, add TLS through a reverse proxy and restrict access by IP; a tunnel is simpler. Full rationale in the security guide.
Dashboard vs. messaging the agent
The dashboard and a chat channel are two front doors to the same agent. Use the dashboard when you want to see and manage — review tasks, audit memory, toggle skills. Use a channel like Telegram when you want to delegate on the go — fire off a job from your phone while the agent works on the server. Most people set up both: the dashboard for oversight, a channel for day-to-day delegation.
Official sources
Checked against the Hermes Agent documentation (v0.21.5) on 2026-09-27. If anything here disagrees with these pages, trust the vendor docs.