overthinkos/openwebui
openwebui/skills/openwebui/SKILL.md
Open WebUI box with auto-configured LLM providers, MCP servers, and Jupyter on port 8080. MUST be invoked before building, deploying, configuring, or troubleshooting the openwebui box.
tools
Updated Jun 22, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins openwebuiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 22, 2026, 7:05 AM170.2s1 file scanned
SKILL.md
- name:
- openwebui
- description:
- |
Box: openwebui
Open WebUI with auto-configured LLM providers (Ollama, OpenRouter), MCP server discovery, and Jupyter code execution. No manual setup needed — secrets auto-managed via charly secrets.
Definition
openwebui:
base: fedora
candy:
- agent-forwarding
- openwebui
- dbus
- charly
ports:
- "8080:8080"
Candy Stack
| Candy | Purpose |
|-------|---------|
| agent-forwarding | SSH + GPG agent forwarding into container |
| openwebui | Open WebUI with auto-config entrypoint |
| dbus | D-Bus session bus |
| charly | OpenCharly CLI for in-container management |
Quick Start
charly box build openwebui
charly config openwebui -e OPENROUTER_API_KEY=sk-or-xxx
charly start openwebui
# Open http://localhost:8080
Deployment Patterns
Standalone with GPG secrets (recommended)
charly secrets gpg setup
charly secrets gpg set OPENROUTER_API_KEY sk-or-xxx
charly box build openwebui
charly config openwebui --env-file .secrets
charly start openwebui
With local Ollama
charly config ollama
charly config openwebui --env-file .secrets --update-all
charly start ollama openwebui
Full workstation (Ollama + Jupyter + Browser)
charly config ollama
charly config jupyter --update-all
charly config selkies-desktop --update-all
charly config openwebui --env-file .secrets --update-all
charly start ollama jupyter selkies-desktop openwebui
Secrets Management
# Tier 1: Auto-generated infrastructure secrets
charly secrets list charly/openwebui
charly secrets get charly/openwebui webui-secret-key
charly secrets set charly/openwebui admin-password --generate
# Tier 2: User API keys (GPG-encrypted)
charly secrets gpg set OPENROUTER_API_KEY sk-or-new-key
charly secrets gpg show
charly config openwebui --env-file .secrets --update-all
Cross-Container Service Discovery
Deploy alongside provider containers for full functionality:
# 1. Deploy ollama (provides OLLAMA_HOST)
charly config ollama
charly start ollama
# 2. Deploy jupyter (provides jupyter MCP server)
charly config jupyter --update-all
charly start jupyter
# 3. Deploy openwebui (consumes both)
charly config openwebui --env-file .secrets --update-all
charly start openwebui
Open WebUI receives:
OLLAMA_BASE_URL=http://charly-ollama:11434— local LLM inferenceTOOL_SERVER_CONNECTIONS=[...]— MCP servers (jupyter + chrome-devtools)CODE_EXECUTION_ENGINE=jupyter— code execution via Jupyter
Key Candies
/charly-openwebui:openwebui— Auto-config entrypoint, secrets, env_accept, TOOL_SERVER_CONNECTIONS format/charly-distros:agent-forwarding— SSH/GPG forwarding
Related Boxes
/charly-jupyter:jupyter— deploy alongside for MCP notebooks and code execution/charly-ollama:ollama— deploy alongside for local LLM inference/charly-hermes:hermes— alternative AI frontend (CLI agent vs web UI)/charly-selkies:selkies-labwc— deploy alongside for shared Chrome browser
Verification
charly status openwebui
charly service status openwebui # openwebui: RUNNING
curl -s -o /dev/null -w '%{http_code}' http://localhost:8080 # 200
charly shell openwebui -c "open-webui version"
# Verify secrets
charly status openwebui # the Secrets: line lists the provisioned charly-openwebui-* engine secrets # webui-secret-key, admin-password
# Verify MCP (inside container process)
charly cmd openwebui "cat /proc/3/environ" | tr '\0' '\n' | grep TOOL_SERVER_CONNECTIONS
Test Coverage
Latest charly check live openwebui run: 24 passed, 0 failed, 0 skipped.
Covers: openwebui entrypoint script presence, pixi python + charly binary,
and deploy-scope: service up, port reachable on 127.0.0.1:${HOST_PORT:8080},
HTTP 200 on / (30-second timeout for first-request startup), admin
email env var injected. See /charly-check:check for the framework.
Related Skills
/charly-openwebui:openwebui— candy authoring/charly-check:check— declarative testing framework/charly-build:secrets— WEBUI_ADMIN_PASSWORD + provider API keys/charly-core:charly-config—-e WEBUI_ADMIN_EMAIL=...deploy-time env setup
When to Use This Skill
MUST be invoked before building, deploying, configuring, or troubleshooting the openwebui box.
Related
/charly-image:image— image family umbrella (candy:image entries — those carryingbase:/from:— incharly.yml, build/validate/inspect/list)/charly-build:build— the embedded build vocabulary (distros, builders, init-systems)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).
SKILL.mdUpdated Jun 14, 2026