Giving Open WebUI eyes, memory, and a mop

What it does Eight self-contained plugins that slot into Open WebUI’s extension points—tools, filters, events, and skills—to add interactive visualizations, database pruning, email composition, and model capability bridges. Each lives in its own folder with a README explaining which components it needs and what problem it solves. The collection targets specific gaps in the default experience, from missing vision support to discarded reasoning context.

The interesting bit The Vision Bridge is particularly clever: it lets a text-only model work with images by stripping them to file-id markers in the request, then exposing an analyze_image tool that pings a separate vision model on demand. Meanwhile, Keep reasoning_content fixes a genuine platform bug where Open WebUI discards a reasoning model’s chain of thought before follow-up turns, causing mid-conversation errors.

Key highlights

• Inline Visualizer v2 renders interactive HTML, SVG, and charts from Chart.js to Tone.js inline in chat, with a nine-color theme-aware palette and conversational drill-down.
• Prune throttles background cleanup of old chats, orphaned uploads, and inactive users so a live instance never hiccups, with dry-run defaults and Redis-coordinated multi-replica support.
• Vision Bridge gives text-only models on-demand image analysis by offloading vision work to a separate model without touching core code.
• Keep reasoning_content feeds prior reasoning back into context for DeepSeek, Kimi, MiMo, and vLLM so tool calls don’t collapse mid-conversation.
• MCP App Bridge renders MCP Apps (SEP-1865) as Rich UI embeds inline, injecting server-declared CSP headers without middleware changes.

Caveats

• Several plugins require Open WebUI 0.10.0 or 0.11.0; version compatibility is explicitly noted per plugin but not summarized globally.
• The Inline Visualizer has a legacy v1 alongside v2, which suggests the API surface may still be shifting.

Verdict Worth browsing if you run Open WebUI in production and have already hit its default limitations—especially around reasoning models, image handling, or database bloat. Skip it if the default Open WebUI already covers your use cases.