Open WebUI Frontend

Point Open WebUI, a self-hosted chat frontend, at Hermes's OpenAI-compatible API server to get a polished browser UI on top of your full agent, with streaming replies and file upload.

Hermes Advanced Copied: 0
1 resource

Requirements

  • The Hermes API server must be enabled, for example via API_SERVER_ENABLED=true and API_SERVER_KEY=....
  • Open WebUI, self-hosted via Docker.

How to use

Open WebUI talks to any OpenAI-compatible endpoint, so pointing it at Hermes puts a browser UI over your full agent — sessions, tools, skills, memory.

Use a long random API_SERVER_KEY. If you expose the port beyond localhost, put TLS in front.

For multi-user access, Open WebUI handles user accounts on its side; Hermes still sees one API client. Per-user sessions on the Hermes side require a different setup (messaging gateways do this better).

  1. Enable the API server in Hermes.
   hermes config set api_server.enabled true
   hermes config set api_server.key "$(openssl rand -hex 32)"   # save this
   hermes gateway install

The API server listens on port 8642 by default.

  1. Run Open WebUI via Docker, pointed at Hermes.
   # docker-compose.yml
   services:
     open-webui:
       image: ghcr.io/open-webui/open-webui:main
       ports: ["3000:8080"]
       environment:
         OPENAI_API_BASE_URL: http://host.docker.internal:8642/v1
         OPENAI_API_KEY: YOUR_API_SERVER_KEY
       extra_hosts:
         - "host.docker.internal:host-gateway"

   docker compose up -d

  1. Open http://localhost:3000, finish the first-run admin setup, and start chatting. Conversations persist because Hermes keeps session state — closing the browser doesn't reset context.

Source: aliaihub/awesome-hermes-usecases and its contributors. License: CC-BY-4.0. Source license notice.

Translation and editorial adaptation by ClawCases.

>Resources

>Related Use Cases

>More at this level: Advanced