Open WebUI

Integrate Intutic governance with Open WebUI — the web interface for LLMs.

How it works

intutic gates install writes a Python filter, ~/.open-webui/intutic-governance-filter.py, that an Open WebUI admin adds once as a Function (Admin → Settings → Functions → + New Function, paste the file). The filter sees each prompt and refuses it when it matches a snapshot rule marked block. Open WebUI loads filters only through its admin UI, so Intutic cannot install it into a running instance.

Setup

1. Initialize Intutic

Open WebUI runs as a server (usually in Docker), so intutic init cannot detect it. Add "open-webui" to the harnesses list in ~/.intutic/config.json yourself (create the file with intutic init first).

intutic init writes no harness files. The files described on this page are written by intutic gates install (open core, no control plane), from the rule sets in .intutic/sops/ — see What writes harness files:

intutic gates install

2. Start the proxy

intutic start

What gets written

Intutic generates:

• Filter: ~/.open-webui/intutic-governance-filter.py — paste it into Open WebUI as a Function (see above).
• Notes: .intutic/env/open-webui.env in the workspace, with the same installation steps.

Open WebUI has no instructions file: system prompts live in its own settings, so the text of your rule sets does not reach the model. The filter still refuses prompts that match a block rule. See Where rule sets go.

To undo what intutic gates install writes here, run intutic disconnect --harness open-webui: each file goes back to what it held before Intutic first wrote it, or is deleted if Intutic created it, and edits you made since are kept. See intutic disconnect.