Open Webui Vibeos
Wire Open WebUI to VibeOS via the API server.
Skill metadata
| Source | Bundled (installed by default) |
| Path | skills/devops/open-webui-vibeos |
| Version | 1.0.0 |
| Author | VibeOS |
| License | MIT |
| Platforms | linux, macos |
| Tags | open-webui, api, frontend, automation |
| Related skills | vibeos-api-automation, cursor-capabilities-bridge, analytical-ui |
Reference: full SKILL.md
信息
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_KEYin~/.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
| Piece | Default |
|---|---|
| VibeOS API | http://127.0.0.1:8642/v1 |
| Open WebUI | http://127.0.0.1:8080 |
| Docs | website/docs/user-guide/messaging/open-webui.md |
| Bootstrap | scripts/setup_open_webui.sh |
| CLI client | `vibeos api chat |
Procedure
- Ensure API server env flags are set (script does this).
- Restart gateway so
:8642listens. - Install/start Open WebUI via the script launcher.
- In Open WebUI → connections: base URL
/v1, bearer =API_SERVER_KEY. - 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_PORTper 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