Academy → Using HermesOfficial documentation · clear explanation

Open WebUI

Open WebUI

Developer13 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Open WebUI 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

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 hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Architecture, Quick Setup, 1. Enable the API server, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Open WebUI 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.
Lesson terms

Short definitions before the details.

Gateway
The process that connects Hermes to channels such as Telegram or Discord and routes messages.
Official page description

Connect Open WebUI to Hermes Agent via the OpenAI-compatible API server

Topic map

What does the source say, and in what order?

  1. 01
    Architecture

    Start here to understand the core idea or structure.

  2. 02
    Quick Setup

    Read this after the foundation, then connect it to the previous step.

  3. 03
    1. Enable the API server

    Read this after the foundation, then connect it to the previous step.

  4. 04
    2. Start Hermes Agent gateway

    Read this after the foundation, then connect it to the previous step.

  5. 05
    3. Verify the API server is reachable

    Read this after the foundation, then connect it to the previous step.

  6. 06
    4. Start Open WebUI

    Read this after the foundation, then connect it to the previous step.

  7. 07
    5. Open the UI

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Docker Compose Setup

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Configuring via the Admin UI

    Read this after the foundation, then connect it to the previous step.

  10. 10
    API Type: Chat Completions vs Responses

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

Open WebUI connects to Hermes Agent's API server just like it would connect to OpenAI. Hermes handles the requests with its full toolset — terminal, file operations, web search, memory, skills — and returns the final response. :::important Runtime location The API server is a **Hermes agent runtime**, not a pure LLM proxy. For each request, Hermes creates a server-side `AIAgent` on the API-server host. Tool calls run where that API server is running. For example, if a laptop points Open WebUI or another OpenAI-compatible client at a Hermes API server on a remote machine, `pwd`, file tools, b
`hermes config set` auto-routes the flag to `config.yaml` and the secret to `~/.hermes/.env`. If the gateway is already running, restart it so the change takes effect:
### 2. Start Hermes Agent gateway
Try it now

Read 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.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Open WebUI” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?