Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix Hermes Open WebUI bootstrap needs clearer privacy warning and uninstall docs [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#25276•Fetched 2026-05-14 03:47:37
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
TReillyCodesTReillyCodes
Participants
TReillyCodesTReillyCodes
Timeline (top)
labeled ×3cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #25286: docs(open-webui): document bootstrap scope, data exposure, and uninstall (#25276)

Description (problem / solution / changelog)

Summary

Issue #25276 asked for five specific clarifications about the Open WebUI bootstrap. This PR extends website/docs/user-guide/messaging/open-webui.md to answer each one. Documentation only — no source files or tests touched.

What #25276 asked for, and where it now lives

AskSection added
Warn that Open WebUI is a third-party frontend, not Hermes Desktop:::warning Third-party frontend admonition at the top
Exactly what the bootstrap changes in ~/.hermesNew "What the bootstrap touches" — enumerates .env keys upserted, log paths, plus every file written outside ~/.hermes (venv, launcher, data dir, launchd plist, systemd-user unit)
Exactly what Open WebUI can read from Hermes configNew "What Open WebUI can read from Hermes" — names the only two channels (launcher reads API_SERVER_KEY only; HTTP client talks to /v1/*) and explicitly lists what Open WebUI cannot see (Telegram/Discord/Slack/WeCom tokens, profile config, memory/skills)
Whether Telegram bot tokens / chat IDs / API settings can be exposedSame section — bullet "Telegram/Discord/Slack/WeCom bot tokens, chat IDs, or any other entries in ~/.hermes/.env other than API_SERVER_KEY"
How to fully uninstall Open WebUI on macOSNew "Uninstalling Open WebUI" → macOS subsection (launchctl bootout + plist + venv + data dir), with a parallel Linux subsection and an optional "also disable the Hermes API server" step

Verification

I cross-checked each documented path against scripts/setup_open_webui.sh:

  • OPEN_WEBUI_VENV default = $HOME/.local/open-webui-venv
  • LAUNCHER_PATH = $HOME/.local/bin/start-open-webui-hermes.sh
  • OPEN_WEBUI_DATA_DIR default = $HOME/.local/share/open-webui/data
  • macOS plist = $HOME/Library/LaunchAgents/ai.openwebui.hermes.plist
  • Linux unit = $HOME/.config/systemd/user/openwebui-hermes.service
  • ~/.hermes/.env keys upserted: API_SERVER_ENABLED, API_SERVER_HOST, API_SERVER_PORT, API_SERVER_KEY, API_SERVER_MODEL_NAME (chmod 600)
  • Launcher only reads API_SERVER_KEY from .env and exports it as OPENAI_API_KEY; no other Hermes env is forwarded into Open WebUI's process.

Net change: 1 file, +85 / -0 lines. The existing setup, troubleshooting, and multi-user-profiles sections are unchanged.

Test plan

  • Reread the diff against scripts/setup_open_webui.sh to make sure every claim is sourced from the script
  • Confirm no source/test files are touched (`git diff --stat` shows 1 doc file)
  • Markdown admonition syntax (:::warning/:::important) matches existing usage elsewhere in this file

Related

  • Fixes #25276

Changed files

  • website/docs/user-guide/messaging/open-webui.md (modified, +85/-0)
RAW_BUFFERClick to expand / collapse

The Hermes Open WebUI bootstrap installed Open WebUI, configured Hermes API settings, restarted the gateway, and created Open WebUI local secrets/storage. This path is easy to confuse with a Hermes-native UI.

Please document:

  • exactly what the bootstrap changes in ~/.hermes;
  • exactly what Open WebUI can read from Hermes config;
  • whether Telegram bot tokens/chat IDs/API settings can be exposed to Open WebUI;
  • how to fully uninstall Open WebUI from macOS;
  • a warning that Open WebUI is a third-party frontend, not Hermes Desktop or Hermes WebUI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#retriever error#indexing error#inference speed#output truncation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING