Hermes Agent Web UI Guide: Dashboard and Gateway Setup
Use the Hermes Agent dashboard, Web UI, and gateway in the right order: install dashboard extras, verify the local UI, check messaging gateway status, and choose hosting when uptime matters.
Hermes Agent Web UI and gateway searches point to two surfaces
The searches Hermes Agent webui, Hermes Agent dashboard, and Hermes gateway are related, but they do not mean the same thing.
Hermes Agent has:
- a browser-based dashboard for configuration, API keys, sessions, logs, and local status
- a messaging gateway that connects the runtime to platforms and long-running delivery paths
Treat them separately during setup. If the base Hermes install cannot run one plain chat yet, adding dashboard and gateway debugging at the same time only makes the failure harder to isolate.
Start with the dashboard after the base install works
The official Hermes dashboard command is:
hermes dashboard
The dashboard starts a local web server and opens the browser interface on localhost by default.
The web dashboard has optional dependencies. If the dashboard command tells you the web stack is missing, install the documented dashboard extras before you keep debugging UI behavior:
pip install 'hermes-agent[web,pty]'
For users who already need a broader Hermes feature set, the official docs also describe the all-extras install path. The important point is simpler: a working CLI install does not automatically prove the optional dashboard stack is present.
What the Hermes dashboard is for
Use the dashboard when you need to:
- see local Hermes status
- manage configuration and API keys
- inspect recent sessions and logs
- monitor gateway state from a browser surface
- use the browser UI instead of editing YAML first
The dashboard is an admin surface. Keep the first check local, especially before you understand how secrets, sessions, and gateway controls are exposed.
Dashboard vs gateway
| Surface | Main job | First command to check |
|---|---|---|
| Web dashboard | Local browser UI for config, keys, sessions, logs, and status | hermes dashboard |
| Messaging gateway | Long-running messaging and delivery process | hermes gateway status |
If the dashboard loads but Telegram, Discord, Slack, or another channel does not behave, the problem may be gateway setup rather than the Web UI itself.
Check the gateway in a clean order
The official messaging docs expose the gateway commands directly:
hermes gateway setup
hermes gateway
hermes gateway status
Use that order intentionally:
- configure the relevant messaging platform
- run the gateway in the foreground when you want visible startup errors
- check status when you expect a service-backed gateway path
Only install or restart a long-running service after you know the runtime, provider setup, and channel credentials are valid enough for the first workflow.
Common setup failures
When the Web UI or gateway path looks broken, check the smallest layer that can disprove the failure:
- plain Hermes CLI chat fails: fix install and model setup first
- dashboard command complains about missing web dependencies: install the dashboard extras
- dashboard loads but channels do not: check gateway setup and status
- channel connects but the workflow stalls after restart: check service behavior, config, and credentials
- dashboard exposure is the next step: stop and decide how the admin surface should be protected
This keeps a dashboard query from turning into a full hosting incident.
When hosted Hermes is the better next step
Local dashboard and gateway setup are useful for learning Hermes Agent.
They become a weak default when:
- the gateway needs uptime beyond one workstation
- scheduled workflows should survive laptop sleep and reboot patterns
- memory, skills, tools, and credentials should not live on a personal device
- the team wants the workflow without maintaining the host
That is where Hermes Agent hosting and managed Hermes Agent become the more relevant comparison.
FAQ
Does Hermes Agent have a Web UI?
Yes. Hermes documents a browser-based Web Dashboard that starts with hermes dashboard.
Is the dashboard the same as the Hermes gateway?
No. The dashboard is the browser admin UI. The gateway is the long-running messaging path and has its own setup and status commands.
Should I expose the dashboard publicly?
Treat the dashboard as an admin surface. Start local and follow the official dashboard guidance before changing bind or exposure settings.