From 620b79477058ebaf5376669091c08abf5456b231 Mon Sep 17 00:00:00 2001 From: sr-dotcom Date: Fri, 26 Jun 2026 16:12:45 -0400 Subject: [PATCH 1/3] docs(quickstart): clarify WebUI runs the agent in-process, not via an external API server HERMES_API_URL is only read by the Tasks/cron health probe (api/agent_health.py) and does not route chat. Adds a plain-language note to Quick Start with the two supported options for users who run an external endpoint. Closes #3873. --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index f0f78a99..55e5063b 100644 --- a/README.md +++ b/README.md @@ -145,6 +145,19 @@ For self-hosted VM or homelab installs, `ctl.sh` wraps the common daemon lifecyc > > `./ctl.sh stop` cannot stop a server launched by `bootstrap.py` or `start.sh` directly — it only manages processes it started itself. +> **How chat runs by default.** WebUI runs the Hermes agent in-process, reading +> your `HERMES_HOME` config directly. It does not connect to an external +> Hermes/agent OpenAI-compatible API server to run chat. `HERMES_API_URL` is only +> read by the Tasks/cron health probe and does not route chat. +> +> Two options if you run an external endpoint: +> +> 1. **Use its models as a chat provider** (supported today): add it in +> **Settings → Providers** as a custom OpenAI-compatible provider with +> `base_url = http://127.0.0.1:8642/v1` and your bearer token. +> 2. **Delegate the whole agent loop to an external runtime**: not how Quick Start +> works today. Tracked in [#1925](https://github.com/nesquena/hermes-webui/issues/1925). + ### Advanced: dynamic recall prefill & Gateway-backed chat Two optional, self-hosted-deployment features — attaching dynamic **session-recall prefill** to browser turns (Joplin/Obsidian/Notion/llm-wiki routers), and routing browser chat through a running **Hermes Gateway** — are documented in [`docs/advanced-chat-setup.md`](docs/advanced-chat-setup.md). Most users need neither. From ec14a78320b72ff913b6074d00e9638ef22e8a6e Mon Sep 17 00:00:00 2001 From: sr-dotcom Date: Fri, 26 Jun 2026 17:03:06 -0400 Subject: [PATCH 2/3] fix(quickstart): clarify HERMES_WEBUI_CHAT_BACKEND=gateway is available today The previous wording implied external gateway routing was not yet possible. HERMES_WEBUI_CHAT_BACKEND=gateway already ships; updated wording distinguishes it from full agent-loop delegation, which is not yet shipped and tracked in #1925. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 55e5063b..28440ca7 100644 --- a/README.md +++ b/README.md @@ -155,8 +155,9 @@ For self-hosted VM or homelab installs, `ctl.sh` wraps the common daemon lifecyc > 1. **Use its models as a chat provider** (supported today): add it in > **Settings → Providers** as a custom OpenAI-compatible provider with > `base_url = http://127.0.0.1:8642/v1` and your bearer token. -> 2. **Delegate the whole agent loop to an external runtime**: not how Quick Start -> works today. Tracked in [#1925](https://github.com/nesquena/hermes-webui/issues/1925). +> 2. **Route chat through a Hermes Gateway API server** (supported today via +> `HERMES_WEBUI_CHAT_BACKEND=gateway`): see [`docs/advanced-chat-setup.md`](docs/advanced-chat-setup.md). +> Full agent-loop delegation is not yet shipped; tracked in [#1925](https://github.com/nesquena/hermes-webui/issues/1925). ### Advanced: dynamic recall prefill & Gateway-backed chat From f2c8ce30c14ab4aeb6aa9c680224cb1c1b405b65 Mon Sep 17 00:00:00 2001 From: nesquena-hermes Date: Fri, 26 Jun 2026 21:32:36 +0000 Subject: [PATCH 3/3] Release YR (v0.51.688): README clarify in-process chat + HERMES_API_URL scope (#5015) Co-authored-by: sr-dotcom --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 238ce45d..b30581a9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,12 @@ ## [Unreleased] +## [v0.51.688] — 2026-06-26 — Release YR (docs: clarify how WebUI chat runs by default) + +### Changed + +- **README: clarified that WebUI runs the Hermes agent in-process by default** (reading `HERMES_HOME` directly) rather than connecting to an external Hermes/agent OpenAI-compatible API server, and that `HERMES_API_URL` is only read by the Tasks/cron health probe — it does not route chat. Documents the two supported options for an external endpoint (add it as a custom OpenAI-compatible chat provider, or route chat through a Hermes Gateway via `HERMES_WEBUI_CHAT_BACKEND=gateway`, see `docs/advanced-chat-setup.md`). Addresses a recurring user confusion (#3873). Thanks @sr-dotcom. (#5015) + ## [v0.51.687] — 2026-06-26 — Release YQ (system-health CPU/RAM metrics work on macOS and other non-procfs platforms) ### Fixed