Libre WebUI integration

Connect Libre WebUI to the Libre Claw daemon for a browser control surface with run timelines, inline tool approvals, automations, and provider usage.

A browser control surface for Libre Claw.

Libre WebUI is a privacy-first, self-hosted AI chat interface built by Kroonen AI. Since the 0.12 release it ships a first-class Libre Claw agent surface: a dedicated sidebar entry, a /agents route, and admin-only backend routes that proxy the local daemon. Your agent runtime, safety model, memory, tools, and schedules stay in Libre Claw; Libre WebUI adds the browser on top.

Source and setup live at github.com/libre-webui/libre-webui, Integration guide (31-LIBRE_CLAW_INTEGRATION.md) 31-LIBRE_CLAW_INTEGRATION.md.

Start the daemon

Libre WebUI talks to the Libre Claw daemon over localhost. Start it the usual way, then open the agent page in WebUI.

Start Libre Claw

libre-claw start
# daemon listens at:
http://127.0.0.1:8766

Then open Libre WebUI → Libre Claw connects to http://127.0.0.1:8766.

Point WebUI at a custom daemon

If the daemon runs on another host or port, set the backend environment variables before starting Libre WebUI.

backend/.env

LIBRE_CLAW_BASE_URL=http://127.0.0.1:8766
LIBRE_CLAW_TIMEOUT_MS=30000

Restart the WebUI backend so the new values take effect.

What the agent page can do

Run timelines

Start chat or goal-mode runs, pass provider/model overrides, stream incremental events, inspect tool calls and results, and cancel active runs.

Inline approvals

Resolve tool permission requests from the browser: allow once, deny, or always allow a tool without leaving the page.

Automations

Create, update, run now, pause, resume, and delete scheduled report and Telegram routes.

Usage

Inspect provider usage records and fallback route state from the same agent page.

Model routing

Switch the active provider and model, and review fallback slots, through admin-only proxy routes.

Daemon status

See connection status, health, and the dashboard URL without leaving Libre WebUI.

How it fits together

Libre WebUI is the browser; Libre Claw is the runtime. WebUI's backend calls admin-only routes under /api/libre-claw that proxy the daemon — nothing about the agent, memory, or safety model is duplicated. Approvals, durable runs, JSONL logs, and schedules all still live in Libre Claw.

Admin-only

The Libre Claw proxy routes are admin-only. The first account created on a fresh Libre WebUI install becomes the administrator, so the agent surface is gated behind the same auth as the rest of the app.