73 wires and counting

$ follow Open WebUI

Keep up with Open WebUI in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-26
stories 62

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Open WebUI 0.11.1 adds human-in-the-loop tool approval

By RepoJournal · Filed · About Open WebUI

Open WebUI 0.11.1 introduces optional human-in-the-loop tool approval, letting users pause tool execution for per-call confirmation, alongside performance optimizations for tool specs and streaming.

Open WebUI v0.11.1 ships a new human-in-the-loop tool approval feature. When an administrator enables it, you can switch a conversation from letting tools run freely to asking first, so a model wanting to use a tool stops and waits for your allow or deny, one call at a time in a saved conversation, by button or keyboard shortcut. Your choice is remembered for the conversation and future ones, and switching back to running freely releases anything already waiting. Automations and channel messages are also covered [1].

Two performance PRs target the chat path. Builtin tool specs were deep-copied per request because callers mutate what they get; the builder now caches the spec already serialized, so a request only parses it back into the independent tree callers need [2]. Separately, every streamed delta was saving a snapshot of the in-progress response by rebuilding the assistant text from scratch, and on the Chat Completions path that re-joined every accumulated chunk even for saves with no new text, so a long answer followed by a large tool call re-joined the whole answer per argument chunk. That re-copy is stopped; the Responses API path already avoided collecting those chunks [3]. The same author says the spec cache change means "the cached value becomes an immutable string, so a request c [source: https://github.com/open-webui/open-webui/commit/b1bfc1876229cf3be8bc993428d8d09f9e807e02]" [2].

Web fetch address checks moved onto the request path. The fetchable-address test and the operator's WEB_FETCH_FILTER_LIST previously ran only where a URL was first validated; both now run on every request. _SSRFSafeResolver is replaced by _SSRFSafeConnector, which hooks _resolve_host to cover aiohttp's IP-literal shortcut and both DNS cache paths, and the filter list runs per request on each transport [4].

Finally, new pt-BR translations cover items introduced in recent releases, with a consistency pass across grammar, tone, capitalization, and pluralization. No logic changed [5].

Action items

References

  1. [1] v0.11.1 ↗ open-webui/open-webui
  2. [2] perf: cache the serialized builtin tool spec instead of deep-copying it per request (#28860) ↗ open-webui/open-webui
  3. [3] perf: stop re-copying the response text on every stream save (#28821) ↗ open-webui/open-webui
  4. [4] refac: consolidate the web fetch address checks onto the request path ↗ open-webui/open-webui
  5. [5] i18n: add pt-BR translations for newly added UI items and consistency pass ↗ open-webui/open-webui

Quick answers

What shipped in Open WebUI on August 26, 2026?
Open WebUI 0.11.1 introduces optional human-in-the-loop tool approval, letting users pause tool execution for per-call confirmation, alongside performance optimizations for tool specs and streaming. In total, 51 commits, 10 pull requests, and 1 releases landed.
Who contributed to Open WebUI on August 26, 2026?
3 developers shipped this update, including github-actions[bot], Classic298, and joaoback.
What were the notable Open WebUI updates?
v0.11.1, perf: cache the serialized builtin tool spec instead of deep-copying it per request (#28860), and perf: stop re-copying the response text on every stream save (#28821).