Skip to main content

Open Webui Vibeos

Wire Open WebUI to VibeOS via the API server.

Skill metadata​

SourceBundled (installed by default)
Pathskills/devops/open-webui-vibeos
Version1.0.0
AuthorVibeOS
LicenseMIT
Platformslinux, macos
Tagsopen-webui, api, frontend, automation
Related skillsvibeos-api-automation, cursor-capabilities-bridge, analytical-ui

Reference: full SKILL.md​

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Open WebUI + VibeOS

Connect Open WebUI to the VibeOS API server for a polished chat UI. Prefer the bundled bootstrap script over hand-rolled Docker unless the user asks for containers.

When to Use​

  • User wants Open WebUI / LobeChat-style frontend on top of VibeOS
  • After enabling API_SERVER_* and needing a browser UI

Prerequisites​

  • Repo checkout with scripts/setup_open_webui.sh
  • Or manual: API_SERVER_ENABLED=true + API_SERVER_KEY in ~/.vibeos/.env
  • Running gateway (vibeos gateway)

How to Run​

One-command bootstrap (preferred):

cd /path/to/VibeOS
bash scripts/setup_open_webui.sh

Manual check:

vibeos api health
# Point Open WebUI connection at http://127.0.0.1:8642/v1
# API key = value of API_SERVER_KEY

Scripted agents should use vibeos api (see vibeos-api-automation) instead of driving the Open WebUI browser.

Quick Reference​

PieceDefault
VibeOS APIhttp://127.0.0.1:8642/v1
Open WebUIhttp://127.0.0.1:8080
Docswebsite/docs/user-guide/messaging/open-webui.md
Bootstrapscripts/setup_open_webui.sh
CLI client`vibeos api chat

Procedure​

  1. Ensure API server env flags are set (script does this).
  2. Restart gateway so :8642 listens.
  3. Install/start Open WebUI via the script launcher.
  4. In Open WebUI → connections: base URL /v1, bearer = API_SERVER_KEY.
  5. Verify with a short chat; tools run on the API-server host.

Pitfalls​

  • Docs that still say ~/.vibeos/vibeos-agent — use this repo path / ~/.vibeos
  • CORS not needed for server-to-server Open WebUI
  • Multi-profile needs distinct API_SERVER_PORT per profile
  • Dashboard API Runs tab (vibeos-runs-inspector) is for ops, not a second chat

Verification​

  • vibeos api health → 200
  • Open WebUI loads model and returns a reply
  • Optional: dashboard → API Runs shows runs created via vibeos api run