Hermes Desktop + Docker Setup (2026)

Do not index

This image illustrates the integration of Hermes Desktop with a Docker backend, showcasing the native app accessible on port 9119 or as a managed service from $3.99/month. Visual elements include a diagram of Docker containers running Hermes Desktop, environment variable HERMES_DASHBOARD=1, port 9119 exposure, and persistent storage mapped to /opt/data. The interface displays status (Running), model details (Hermes-3-Llama-3.1-405B), and performance metrics such as requests (1.2K), tokens processed (512K), and latency (128ms). The branding for Agent 37, the service provider, is prominently displayed alongside a call-to-action button labeled 'Skip Compose'. This image is useful for documentation and knowledge sharing about deploying Hermes Desktop with Docker and understanding its service offering from Agent 37.

Hermes Desktop Docker usually means driving the native Hermes Desktop app against a Hermes agent running in Docker. Install Desktop on your laptop, run nousresearch/hermes-agent with a persistent ~/.hermes → /opt/data volume, enable the dashboard with HERMES_DASHBOARD=1 on port 9119, then add a Remote Gateway in Desktop. That stack is powerful and easy to mis-secure. For always-on Hermes without Compose babysitting, Agent 37 starts at $3.99/mo (1 vCPU, 4 GB RAM, 8 GB storage).

What does hermes desktop docker mean?

Hermes desktop docker mixes two products and two Docker jobs. Sort them before you paste Compose.

Phrase	What it is
Hermes Desktop	Native app (macOS / Linux / Windows) with local or remote backends
Hermes in Docker	Agent + gateway run inside `nousresearch/hermes-agent`
Docker terminal backend	Agent on the host; tool commands run in a sandbox container
Remote Gateway	Desktop talks to a `hermes dashboard` backend on 9119, not the OpenAI-compatible API on 8642

Official Docker guide: Hermes Docker Setup. This page is the Desktop + Docker backend path for the compound search.

Why do people search hermes desktop docker?

People search hermes desktop docker when the native app feels great on a laptop, but channels die when the lid closes. They want Desktop as the UI and Docker (often on a VPS or always-on box) as the runtime.

Common triggers:

A guide said "point Desktop at Remote Gateway"

They already run gateway run in Compose and want a nicer front end

Local Desktop install works, but they need the agent on a server

They confuse port 8642 (API / health) with 9119 (dashboard / Desktop)

If you only need channels online and a browser console, you may not need Desktop + Docker at all. Managed path: Hermes agent hosting.

How do you connect Hermes Desktop to Hermes in Docker?

This image provides a detailed visual guide for connecting a desktop application to Docker Hermes. It outlines four main setup steps: (1) running the Hermes agent container with Docker using a command that includes environment variables for the dashboard and authentication; (2) enabling and monitoring the Hermes dashboard, displaying port number, session count, container count, system status, and uptime; (3) performing user authentication with options for basic auth or OAuth, including signing in via standard credentials or GitHub; and (4) configuring the desktop application by adding a remote gateway with specific settings like URL, authentication type, and testing the connection to ensure successful integration. The image is branded with Agent 37 and includes an illustrated character, offering a professional and clear instructional resource for users managing Docker Hermes connections.

You connect Hermes Desktop to Hermes in Docker by persisting /opt/data, enabling the supervised dashboard, securing auth, then registering a Remote Gateway in the app.

1. One-time Docker setup

mkdir -p ~/.hermes
docker run -it --rm \
  -v ~/.hermes:/opt/data \
  nousresearch/hermes-agent setup

Use SSH on a VPS, not a broken browser console that mangles : and @ in paste.

2. Run gateway + dashboard

docker run -d \
  --name hermes \
  --restart unless-stopped \
  -v ~/.hermes:/opt/data \
  -p 8642:8642 \
  -p 9119:9119 \
  -e HERMES_DASHBOARD=1 \
  nousresearch/hermes-agent gateway run

Or Compose with the same ports, volume, command: gateway run, and HERMES_DASHBOARD=1. Official docs include a full Compose example on the Docker page.

Inside the published image, gateway run is s6-supervised. With HERMES_DASHBOARD=1, the dashboard restarts beside the gateway. Mount stays ~/.hermes:/opt/data. Do not mount over /opt/hermes (immutable app tree).

3. Auth before you expose :9119

In Docker, dashboard host defaults to 0.0.0.0 so published ports work. Non-loopback binds require an auth provider. HERMES_DASHBOARD_INSECURE is a deprecated no-op after the June 2026 hardening.

Homelab / Tailscale shape: set HERMES_DASHBOARD_BASIC_AUTH_USERNAME + HERMES_DASHBOARD_BASIC_AUTH_PASSWORD (and a secret for stable sessions). Prefer Tailscale or SSH tunnel over a public internet bind. OAuth / OIDC options are documented for public-facing deploys.

4. Point Desktop at the container

Install Hermes Desktop on your laptop.

Open Settings → Gateways.

Add Remote gateway.

Use the host URL on port 9119 (LAN IP or Tailscale IP), not 8642.

Smoke test one Chat reply, then one Telegram / Discord / Slack ping if channels matter.

One :9119 connection covers co-located profiles through Desktop's profile switcher. You do not need a second published dashboard port per profile.

Hermes Desktop Docker vs Docker terminal backend vs Agent 37

This image compares two approaches for deploying the Hermes agent: a self-hosted Desktop Docker VPS versus the managed Agent 37 service. It highlights the operational differences where Desktop + Docker requires user management of compose, volumes, authentication, image pulls, and tunneling setup, whereas Agent 37 offers a one-click Hermes agent with per-instance isolation, browser-based terminal and file access, starting at $3.99 per month. The image also includes branding elements and a stylized illustration to visually support the comparison, making it useful for technical decision-making documentation.

Path	Best for	Who owns ops	Price shape
Desktop local only	Day-one UI on your machine	You	$0 host
Desktop + Hermes in Docker	Native UI, always-on container backend	You	About $6 to $12/mo VPS typical
Desktop local + `terminal.backend: docker`	Sandbox tool commands on the same machine	You	$0 host + Docker Desktop
Agent 37 managed Hermes	Always-on isolation + managed console	Platform	From $3.99/mo

Use Desktop + Docker when you want the native app and you will own Compose, volumes, auth, and upgrades (docker compose pull then recreate).

Use Agent 37 when you want an always-on Hermes instance with task board, web terminal, files, and live desktop without operating :9119 yourself. Deploy: deploy Hermes. Product: Hermes hosting.

What breaks first on Hermes Desktop Docker?

Common failures:

Remote Gateway pointed at 8642 instead of 9119

HERMES_DASHBOARD unset, so Desktop has nothing to attach to

No auth provider on a published 0.0.0.0 dashboard (fails closed)

Volume forgotten, so setup and runtime do not share state

Public :9119 without Tailscale / reverse proxy discipline

Expecting Desktop to start the Docker backend for you (it attaches; it does not replace Compose)

Fix order: volume → HERMES_DASHBOARD=1 → auth → correct URL → Chat smoke test → channel ping.

How much does Hermes Desktop Docker cost?

Path	Cash	What you get
Desktop + local Hermes	$0 host	Native UI, sleeps with the laptop
Desktop + Docker on a VPS	About $6 to $12/mo typical	You own image pulls, auth, tunnels
Agent 37 managed Hermes	Basic $3.99/mo; Plus $9.99/mo; Pro $29.99/mo; Max $99.99/mo	Always-on instance + managed console
Model APIs	BYOK or bundled free models on Plus+	ㅤ

Plus adds 12 GB storage and bundled GPT-5.6 Luna, DeepSeek V4 Flash, and Mercury 2 with usage caps. Pro adds Chromium (2 vCPU, 8 GB RAM, 20 GB). Max is 4 vCPU, 16 GB RAM, 40 GB. Cloud API instances for products start from $1.99 per agent per month, billed per minute.

How should agencies think about Hermes Desktop Docker?

Agencies should treat Desktop as an operator UI, not a client portal. One shared Docker host with one published dashboard is a credentials risk. Give each client an isolated instance. White-label: white label AI agents.

Want Hermes online without wiring Desktop to Compose? Start on Agent 37 pricing at $3.99/mo.

Frequently Asked Questions

Can Hermes Desktop talk to Hermes running in Docker?

Yes. Enable the dashboard with HERMES_DASHBOARD=1, publish 9119, configure auth, then add a Remote Gateway in Desktop.

Which port does Hermes Desktop use for Docker?

9119 for the dashboard / Remote Gateway backend. 8642 is the optional OpenAI-compatible API / health port, not the Desktop remote connection.

Is Hermes Desktop Docker the same as terminal.backend docker?

No. Hermes in Docker runs the whole agent in a container. terminal.backend: docker sandboxes tool commands while the agent process stays on the host.

Do I need HERMES_DASHBOARD_INSECURE?

No. It is a deprecated no-op. Configure basic auth, OAuth, or OIDC, or reach loopback over a tunnel.

What volume should I mount?

Host ~/.hermes to container /opt/data. That holds config, .env, sessions, memory, and skills.

Do I need Hermes Desktop Docker on Agent 37?

Not for day-to-day use. Agent 37 gives you a managed console on an always-on Hermes instance. Use Desktop + Docker when you specifically want the native app on a self-hosted container.

What is the cheapest always-on alternative?

Managed Agent 37 Basic at $3.99/mo when the real need is uptime and isolation, not operating Compose and :9119 yourself.

Hermes Desktop Docker: Connect the App to a Container Backend (2026)