hermes dashboard Command — Complete Reference & Examples

Overview

hermes dashboard launches the Hermes Agent web dashboard for managing configuration, API keys, sessions, and embedded chat. You can bind it to a custom host/port, skip the UI build, run an isolated profile-scoped server, or control a running server.

hermes dashboard [register] [options]

Subcommands

`register` — Register a self-hosted dashboard

hermes dashboard register

Registers a self-hosted dashboard with Nous Portal and writes the OAuth client ID to .env.

Options

Option	Description
`--port PORT`	Port to listen on. Default is `9119`. Use `0` to auto-assign a port.
`--host HOST`	Host to bind to. Default is `127.0.0.1`.
`--insecure`	Deprecated / no-op. As of June 2026 hardening, it no longer disables authentication on a public bind. Public binds always require an auth provider; bind `127.0.0.1` and tunnel for local access.
`--skip-build`	Skip the web UI build step and serve the existing `dist/` directly. Useful for non-interactive contexts such as Windows Scheduled Tasks or CI where npm may not be available. Pre-build with `cd web && npm run build`.
`--isolated`	When launched from a named profile, run a dedicated server scoped to that profile instead of attaching to the machine-level server. The default behavior is unified.
`--stop`	Stop all running Hermes web server processes and exit.
`--status`	List running Hermes web server processes and exit.
`--no-open`	Do not open the browser automatically.

Common Scenarios

Launch the dashboard locally

hermes dashboard

Starts the dashboard on http://127.0.0.1:9119 and opens it in your browser.

Use a custom port

hermes dashboard --port 8080

Useful when port 9119 is already occupied.

Run without auto-opening the browser

hermes dashboard --no-open

Useful on remote hosts or when running from a script.

Serve a pre-built UI in CI

cd web && npm run build
cd ..
hermes dashboard --skip-build --no-open

Use --skip-build to avoid npm dependency resolution in headless environments.

Check or stop a running server

hermes dashboard --status
hermes dashboard --stop

Run an isolated profile-scoped dashboard

hermes dashboard --isolated --profile work

Runs a dedicated dashboard server for the work profile instead of sharing the machine-level server.

Tips

The dashboard requires authentication when bound to a non-loopback address; set up an OAuth or password provider first.
Keep the default 127.0.0.1 bind for local-only use and tunnel through SSH for remote access.
--skip-build still needs a valid dist/ directory; pre-build the UI before using it.