Manual install

Install the Pipe by pasting one file into Open WebUI's admin panel and setting a few valves. No script and no credentials shared; you end up where the installer would have left you.

Applies to: Pipe

Valves: GATEWAY_URL, GATEWAY_TOKEN, AGENT_ID, DEVICE_IDENTITY, STATE_DIR, ENABLE_FILE_SERVER, USE_OWUI_FILES, OWUI_BASE_URL, SEND_STOP_ON_CANCEL

Before you start

A running OpenClaw Gateway, reachable from the Open WebUI backend.
Your OpenClaw Gateway API token: the value of gateway.auth.token in your OpenClaw config.
Admin access to Open WebUI in a browser.
Open WebUI must be able to pip-install websockets and cryptography the first time the function loads. If yours can't (offline, or frontmatter installs turned off), see Python packages inside Open WebUI.

Paste the Pipe

An Open WebUI function is one flat .py file. Paste it in the admin panel:

Open Admin Panel → Functions in Open WebUI.
Click + → Create a function with ID openclaw_gateway, type pipe.
Paste the contents of openclaw_pipe.py.
Save, then toggle Active → ON and Global → ON.

Use the ID openclaw_gateway exactly. The Status Action and the installers look the Pipe up by that ID.

Set the valves

Open the function's valves in Admin Panel → Functions and set:

Valve	What to set
`GATEWAY_URL`	OpenClaw Gateway address, `host:port`, no scheme (default: `localhost:18789`). It is resolved by the Open WebUI backend, not by your browser
`GATEWAY_TOKEN`	Your Gateway API token
`AGENT_ID`	Which agent to route to (default: `main`)
`DEVICE_IDENTITY`	Leave empty. The Pipe generates an identity on first connect and keeps it in `STATE_DIR`. Set it only to import an identity that is already approved
`STATE_DIR`	A persistent, writable directory inside the Open WebUI container (default: `/data/openclaw-bridge`). See restart-safe state
`ENABLE_FILE_SERVER`	`True` (media support; the default)
`USE_OWUI_FILES`	`True` (native Open WebUI Files API media support; the default)
`OWUI_BASE_URL`	Open WebUI base URL reachable from the Open WebUI backend (default: `http://127.0.0.1:8080`, right for a standard single-container install)
`SEND_STOP_ON_CANCEL`	`True` (workaround for `chat.abort` not stopping active tool subprocesses; the default)

Only GATEWAY_URL and GATEWAY_TOKEN usually need a change. These are the same valves the installer sets. Every other valve, with its default: Configuration.

Approve the device

The first time the Pipe connects, the Gateway holds the new device until you approve it. Until then a chat answers pairing required. On the Gateway host:

bash

openclaw devices list
openclaw devices approve <request-id>

If no request is pending yet, send one message in a chat first: the Pipe connects on first use. More in device pairing.

Start chatting

Reload Open WebUI, choose OpenClaw · Default (or any discovered model) and start chatting. The reply should stream in token by token.

The Status Action and the thinking filter, by hand

Both are optional and install the same way, as their own functions:

Status button: an Action with ID openclaw_status_action, whose five connection valves must match the Pipe's.
Thinking control: a Filter with ID openclaw_thinking, attached per model.

Agent skills: teach your agent the two conventions the integration listens for.
Update and uninstall: updating by hand, and removing it.

Manual install ​

Before you start ​

Paste the Pipe ​

Set the valves ​

Approve the device ​

Start chatting ​

The Status Action and the thinking filter, by hand ​

Next ​