How to Use Hermes WebUI / Dashboard Safely
Open Hermes WebUI safely, fix common dashboard launch problems, decide when to self-host it, and use FlyHermes when you want a managed dashboard plus Telegram/Discord agent.
Quick answer
Run hermes dashboard after the Hermes CLI works, open the local browser URL, and use --port or --no-open for server workflows. Do not expose WebUI directly to the public internet; use HTTPS, auth, firewall rules, or a private tunnel. If you want a team dashboard plus Telegram/Discord and browser/search workflows without server maintenance, use FlyHermes.
The Hermes Agent dashboard, also called the Web UI or WebUI, gives you a browser-based control surface for sessions, conversation history, files, images, tools, memory, skills, and team demos. It pairs with the CLI, Docker Compose, VS Code, Telegram, Discord, and GitHub workflows rather than replacing them.
Managed cloud · API costs included · Skill library · Cancel anytime
Before you start:
- ☑Hermes Agent installed
- ☑hermes setup completed and hermes doctor passing
- ☑A modern web browser
Steps
- 1
Verify the CLI first
Install Hermes Agent, run hermes setup, then run hermes doctor so provider, config, and local dependencies are healthy before opening the browser dashboard.
- 2
Start the dashboard
Run hermes dashboard. Hermes opens the Web UI in your browser when possible and serves the dashboard locally from the active profile.
- 3
Choose a port or suppress auto-open
Use hermes dashboard --port 9120 when the default port is occupied. Use hermes dashboard --no-open on a VPS, over SSH, or any environment where you want to open the URL manually.
- 4
Check dashboard health
Confirm the Web UI loads, recent sessions appear, and memory, skills, files, tools, or gateway activity render before handing the dashboard to a teammate.
- 5
Secure remote access before sharing
For VPS or team access, put the Web UI behind HTTPS, authentication, a VPN or trusted tunnel, and narrow firewall rules. Treat it as an admin interface, not a public landing page.
Pro Tips
- 💡Use the dashboard for demos and monitoring; keep the CLI available for configuration, provider changes, and deeper debugging
- 💡If macOS or launchd gives Hermes a reduced PATH and the dashboard cannot find npm, build the frontend once from ~/.hermes/hermes-agent/web with npm install and npm run build
- 💡If the frontend is already built but Hermes still cannot find it, launch with HERMES_WEB_DIST=$HOME/.hermes/hermes-agent/hermes_cli/web_dist hermes dashboard
- 💡Use Docker Compose, VPS, Telegram, Discord, GitHub, and VS Code guides for the entry points; use this Web UI guide for browser-based visibility across those workflows
- 💡If a teammate needs browser visibility but you do not want to own HTTPS, auth, firewall rules, process restarts, and model-provider maintenance, price FlyHermes against the self-hosted route
- 💡Never expose the dashboard directly on the public internet without auth, HTTPS, and firewall restrictions
Troubleshooting
❌ Dashboard or Web UI returns 'connection refused' when opening in browser
✅ Start the dashboard with hermes dashboard and check the selected port. If you chose port 9120, open http://127.0.0.1:9120. Verify nothing else is using the port with lsof -i :9120.
❌ Web UI frontend not built and npm is not available
✅ Hermes may be running with a reduced PATH. Check which node and which npm in your shell, then build once manually: cd ~/.hermes/hermes-agent/web && npm install && npm run build. Relaunch hermes dashboard after web_dist exists.
❌ Built dashboard assets exist but Hermes still cannot find them
✅ Point Hermes directly at the built frontend: HERMES_WEB_DIST=$HOME/.hermes/hermes-agent/hermes_cli/web_dist hermes dashboard --port 9120 --no-open.
❌ Dashboard is exposed on a public VPS
✅ Immediately add authentication and HTTPS, restrict the firewall, or move the UI behind a VPN/reverse proxy. Treat it as an admin surface with access to agent actions and history.
FAQ
Is Hermes Web UI the same as the Hermes Agent dashboard?
Yes. People use Hermes Web UI, Hermes WebUI, and Hermes Agent dashboard for the same browser-based interface.
What command opens the Hermes dashboard?
Run hermes dashboard. Add --port 9120 to choose a port or --no-open when running on a server.
Does the dashboard replace the Hermes CLI?
No. The dashboard gives browser visibility and lightweight operation. Keep the CLI for setup, provider changes, debugging, skills, tools, and gateway configuration.
Can I use the dashboard with Telegram, Discord, Docker Compose, VS Code, and GitHub?
Yes. Those integrations are task-entry or deployment surfaces; the dashboard is useful for monitoring the active sessions and state behind them.