Hermes Web Dashboard (localhost:9119)
Not everyone wants to live in a terminal. The Hermes web dashboard gives you a visual window into your agent — its tasks, memory, skills, and channels — at http://localhost:9119. 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.
With the Hermes daemon running, open http://localhost:9119 in a browser on the same machine. If Hermes runs on a VPS, don't expose the port — tunnel to it over SSH (covered below).
What each panel does
- Tasks / Kanban board. See active, queued, and completed tasks. Recent Hermes versions turn this into a multi-agent board where one task can be worked by parallel agents — drag, prioritize, and watch progress live instead of tailing logs.
- Chat / console. Talk to the agent directly from the browser, the same as messaging it on a channel — handy for testing a new skill before wiring it to Telegram or Discord.
- Memory. Browse what the agent remembers — its persistent memory entries and session recall. Useful for spotting stale or wrong facts you want to correct.
- Skills. View installed skills, what each one does, and toggle them. This is where you confirm your allowlist — only the skills you've reviewed should be enabled.
- Channels. See which messaging channels are connected (Telegram, Discord, WhatsApp, Slack) and their status.
- Settings. Model selection, iteration/budget limits, and configuration — the same knobs as the config file, in a form.
Reach it safely from a remote server (SSH tunnel)
The dashboard is powerful — it can read your agent's memory, secrets, and history — and by default it has no authentication. So you never expose port 9119 to the internet. To use it on a VPS, forward the port to your laptop over SSH:
# On your laptop:
ssh -L 9119:localhost: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 (or opening 9119 in your firewall) puts an unauthenticated control panel for your agent on the public internet. Keep it on 127.0.0.1. If you genuinely need browser access without a tunnel, put it behind a reverse proxy (Caddy/nginx) that adds authentication and TLS, and restrict by IP. 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.