v1.0.27

v1.0.27

Inline Visualizer v2.2.0

Important

THE BIG ONE:

Your text is back — and a new Offline mode

On Open WebUI 0.10.x the visualization rendered fine but everything you wrote around it vanished — intro, explanation, all of it (#60). That's fixed, the hiding engine was rebuilt around one rule: never sacrifice your text. And for air-gapped and privacy-focused instances there's a new offline security level: zero outgoing connections, with a README tutorial for self-hosting the chart libraries on your own server. 🚀

Added

• New offline security level — zero outgoing connections, period. Like Strict, but even the three chart-library CDNs are blocked: the visualization can only load scripts from your own Open WebUI server. External images, fonts, and media stay blocked too. Made for air-gapped networks and privacy-focused setups.
• Performance Improvement: 🚀 The Strict and Balanced security headers are assembled once at startup instead of on every render — same output, less work per visualization.
• Self-hosting tutorial in the README — how to keep Chart.js, D3, ECharts & friends working in offline mode: download the library files once, drop them into Open WebUI's /static/iv-libs/ folder (Docker recipe included), and point SKILL.md at the local copies. Visualizations that don't use a library work in offline mode with zero setup.
• Accidental hiding now fixes itself. Whatever the plugin hides in the chat is re-checked on every update and brought back the moment it no longer needs to be hidden — after message edits, re-renders, or a wrong guess about an incoming marker. Previously, once something was hidden it stayed hidden for good.

Fixed

• Entire response hidden on Open WebUI 0.10.x (#60). The visualization rendered fine, but all the text around it — the intro before and the explanation after — disappeared. Cause: Open WebUI 0.10 places the raw visualization source and your prose inside the same container, and the old logic hid that whole container. Happened every time, including when reopening finished chats. Thanks to @NC-Channel-Coder for the report and the perfect repro.
• Second visualization in the same message failing to render. Multiple visualizations in one response now coordinate with each other instead of tripping each other up.
• Text on the same line as a marker being destroyed. Here is the chart: @@@VIZ-START and @@@VIZ-END And that's the takeaway. now keep their words — only the marker itself disappears.
• A code example hijacking the visualization. A documentation snippet containing a marker pair used to get rendered in the iframe instead of the real visualization — which was then hidden and never shown anywhere. A marker mentioned in inline code could even hide the rest of the message.
• Sentences legitimately ending in @@@ disappearing forever.
• Two visualizations back-to-back leaking raw source. When one block ended and the next began without text in between, the second one's source code could show up as plain text in the chat.

Changed

• Hiding rewritten around one rule: never sacrifice your text. The plugin now only hides something outright when everything inside it belongs to the visualization; anything that also contains your text is cleaned up more carefully instead. Images, dividers, and form elements sitting near a visualization are never touched.
• Markers inside code are treated as documentation, not instructions. If a message talks about @@@VIZ-START … @@@VIZ-END in a code block or inline code, that's now simply displayed as code — it no longer triggers hiding or rendering.
• Smarter handling of a trailing @@@. Text ending in @@@ is only treated as a possible incoming marker right at the live stream's tail, while the visualization is still being written. Everywhere else it's just text — and a wrong guess un-hides itself right away.
• Late re-renders can no longer bring hidden source code back. The cleanup that runs after a visualization finishes now stays active and re-hides anything the chat restores afterwards.

Prune v0.10.10

Added

• See exactly what a Preview would delete. Every nonzero category on the /prune page now expands into a paginated list of the actual records behind the number — ids, owners, and titles, 50 or 100 per page — and the whole list can be exported as JSON for an audit trail. Exports larger than 10,000 items ask for confirmation first. Contributed by @FBH93 (#61) — thank you!
• Cancel a running pass. A Cancel button appears on the manual page while a Preview or Execute is running (with a matching API endpoint). Cancellation is deliberately gentle: the pass stops at the next batch boundary, never mid-transaction — anything already deleted stays deleted, nothing is left half-done, and simply re-running finishes the job. A stale cancel can never abort a later run.

Fixed

• The JSON export could silently miss records on PostgreSQL. Detail pages had no fixed ordering, so page boundaries could shift between requests and drop rows from an export. Pages are now ordered by primary key — a full export walk is complete and duplicate-free.
• Full exports were painfully slow on big tables. Each page used to re-walk the table from row zero and re-fetch the whole user list. Sequential pages now resume where the previous one stopped, and the heavy classification work is reused for the duration of an export.
• The audio-cache scan could freeze the instance for a moment and even error out if another cleanup removed files mid-scan. It now runs off the main loop and shrugs off vanishing files.
• Whole-database detail listings now require the same authentication as Preview and Execute — they were reachable with cookie-only auth before. Nothing changes for the admin page itself.

Changed

• Faster vector-collection scans (Milvus/Qdrant), a leaner PGVector memory scan, and the /prune page is served from a pre-built template instead of being reassembled on every load. All output is byte-for-byte identical — these are pure speed-ups.

Inline Visualizer (v1 - Legacy) v1.5.0

Added

• Performance Improvement: The Strict and Balanced security headers are assembled once at startup instead of on every render — same output, less work per visualization. No functional changes.