Web Dashboard
Web Dashboard
Start with meaning, then move to detail.
This lesson explains Web Dashboard as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Quick Start, Options, Managing multiple profiles, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Web Dashboard without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Browser-based administration panel for managing configuration, API keys, MCP servers, messaging pairing, webhooks, the gateway, memory, credentials, sessions, logs, analytics, cron jobs, and skills
What does the source say, and in what order?
- 01Quick Start
Start here to understand the core idea or structure.
- 02Options
Read this after the foundation, then connect it to the previous step.
- 03Managing multiple profiles
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 05Pages
Read this after the foundation, then connect it to the previous step.
- 06Status
Read this after the foundation, then connect it to the previous step.
- 07Chat
Read this after the foundation, then connect it to the previous step.
- 08Connecting Hermes Desktop to a remote backend
Read this after the foundation, then connect it to the previous step.
- 09Remote dashboard setup
Read this after the foundation, then connect it to the previous step.
- 10Config
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes dashboard# Custom port
hermes dashboard --port 8080
# Bind to all interfaces (use with caution on shared networks)
hermes dashboard --host 0.0.0.0
# Start without opening browser
hermes dashboard --no-openworker dashboard
# → already running: opens the browser at ?profile=worker
# → not running: starts the machine dashboard with "worker" preselectedRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.