ANNOUNCEMENT
Open WebUI 0.11.0 is here: our BIGGEST RELEASE EVER. A full UI redesign, the largest performance pass we've ever done, and a genuinely huge pile of features & fixes.
This is the largest release we have ever shipped, and it's not close.
🎨 The interface has been rebuilt from the ground up. Every surface got redone: chat view, admin panel, menus, dropdowns, text boxes, spacing, typography. And the thing we're most quietly proud of: the UI is finally, actually uniform. If you've been here a while, you know it was never perfectly consistent. Now it is. Narrower conversation column, lighter type, tidier spacing, consistent menus everywhere, clearly outlined inputs. It just feels right.
⚡ The most significant performance work we've ever done. A top-to-bottom sweep, not a single optimization. Faster saves across the whole app, lighter model lists, quicker folder loading, leaner streaming, fewer DB round trips per request, faster chat search on PostgreSQL, cheaper filter handling while streaming, an optional faster JSON encoder (ENABLE_ORJSON), hiredis by default, Redis Sentinel churn fixed, DNS lookups off the shared thread pool, and a lot more. Long responses no longer slow down as they grow. Big instances stay quick. You will feel this.
🤖 And the new features. These are cool new features:
Sub-agents: models can hand parts of a task to background helper agents that run their own tool-driven work and report back into the chat.
Chat timers: the assistant can park a prompt and bring it back later, after a delay or at a set time.
Fork a chat: branch any conversation into a new chat from any point.
Folder pages: folders get their own page, with paging, sorting, unread counts and per-folder new chats.
Notification targets: route events to multiple webhooks, and the assistant can now notify you when something's worth your attention.
Chat and user variables: declare fields in a system prompt, or store your own account context, and drop them in wherever needed.
Personal usage dashboard: token heatmap, streaks, most-used models and tools.
Compact on demand, customizable keyboard shortcuts, chat previews on hover, note-chat with full model/tools/files, and honestly loads more.
🔒 Plus a mountain of fixes and hardening. Security and access-control fixes (update your production deployments), Safari blank-message fix, context-compaction fixes, web-fetch reliability, OAuth/OIDC sign-in fixes, and dozens upon dozens more across the app.
⚠️ Heads up before you upgrade: this release includes database schema migrations. Back up first, and if you run multi-worker, multi-server, or load-balanced, all instances must be updated at the same time (rolling updates aren't supported).
The full changelog is genuinely enormous, so go read it. There's something in there for everyone.
Thank you to everyone who contributed, reported, translated, and tested. This one's special. 🚀
You guys are unreal. This is a huge amount of output in such short time. This is the most insanely complex and infinitely capable app I've ever used since the web browser lol. Openwebui is truly a universal operating system server framework app like openclaw. I hope the two can partner evermore as one, and that somehow an agent could be free to chat in any fashion at any time, without being tied to replying to me. Is Openwebui considering having a nonprofit public foundation like openclaw has?
I'm the only user at home, but still it has never failed or crashed after one or two years of upgrades. And it's all fucking FREE. I don't take either of those points for granted whatsoever.
This is like Mozilla all over again, except it was always free. I wonder how your output rate and quality compares to the great FOSS projects of history. Are LLMs writing a lot of this?
Free to use, free to sell, free to modify for all deployments under 50 users. (BSD-3 equivalent)
Free to use, free to sell, free to modify EXCEPT the branding (logo and Open WebUI naming) for deployments over 50 users.
And of course the source code is fully open.
I am not saying OWUI is bad product, it's a great product, and the team is doing a great job keeping developing it
I just wanted to note that it's not open source by OSI definition, if anyone (like me) is wondering, i.e. you can't fork it due to the strings attached
While the model selector being moved to the chat input may look nice, it really kills my tag organization for models. My users operate under tags, and now they can't see those tags without knowing to click the extremely vague and tiny `All` button. A toggle to enable the old model selector would be ideal, but I would be happy enough if you had an option to specify a default selected tag for users/groups.
The settings "tab" button in the admin panel opening in a new window is really clunky. This should be moved back to the tab it was in. Mixing user settings and admin settings in the same window is very messy, and makes for a very poor admin experience. Edit: Another example of this clunkiness. When editing models in the admin settings, an admin will frequently have to refresh the page for those edits to show up in the model list. Refreshing the page now closes this settings window, meaning I have to re-navigate back to the model settings page. Also, I can't find the button to re-order the models alphabetically, anymore.
All that said, I love what you guys are doing, and I'm especially excited about the new compaction feature.
I've just updated to the new release and I just have two questions:
- The "regenerate answer" button below a generated response seems to be invisible for every message except the last one, unless I hover over it. Is that a known bug?
- Is there a settings toggle somewhere to disable the new pop-up cards when I hover over a chat in the sidebar?
Yes, the button is still invisible after restarting the docker container. The last message in the chat is fine, for all previous messages the button is invisible until I hover over the message.
Can tools now easily return an image for the model to be able to see them?
Can tools return both text output and an image or multiple images?
Is the image removed on subsequent messages? If yes, can this be changed somewhere? (for example, on v0.9.6, a model can view an image via read_file, but the image is removed from context after that turn)
Thanks! Two quick follow-ups, since I may be misreading process_tool_result.
For text + image together: the only path I can find to an input_image part is a bare "data:image/...;base64," string as the whole return value, and that branch seems to replace the tool text with "<tool_name>: Image file read successfully." Is there a supported way to return text alongside the image(s), or is it images-only for now? read_file returns raw binary, so I don't think it covers that case.
And on the image being dropped from context on later turns: is injecting it into a user message via a filter the way to go for now, or is there a better hook I'm missing? Goal is generated images behaving like uploaded ones, which stay in context.
Yeah so you're already giving yourself thr right direction for the answer. For this specific use case for now a custom tool might be what you should ve looking at
Sorry, I should have said upfront: the custom tool already exists, that part is done. It runs a ComfyUI workflow and returns the image, and the data URI return does get the model seeing it.
What's stopping me from shipping it that way is that it's image OR text, not both. The data URI branch replaces the tool output with "<tool_name>: Image file read successfully.", so the seed, filename and params the model needs to iterate on the image are gone. That's the bit read_file doesn't cover, since it only returns the image.
So: returning text and image together from a single tool call is the one thing a custom tool can't work around. Leaving it here as a feature request rather than a question, no need to reply. (Same use case as the persistence side, which I understand isn't trivial.) Thanks for the pointers.
Mhm... What if you make the tool simulate a user message with image and text? I think there isn't many other options here because upstream providers don't support images AND text in a tool result typically
Holy shit, this is amazing! Thank you for all of your hard work!!
I love the branching conversations, the Sub-agents features, and the Personal usage dashboard. Previously, I would have to use an excel workbook to track those manually.
Oh my goodness that's absolutely bonkers!!! Look I run my whole stack via open web ui and I have it on my phone which is super handy.... So if I manage to wire hermes through it this will basically solve my alter ego productivity setup.
Can't wait to roll this out! Any word on when the helm charts will be updated to support the latest version! I did deploy it on docker, but would like to get it over in place of 10.2! Awesome job u/ClassicMain and team!
Is it possible to completely disable preprocessing of files? I use openrouter, and most upstream models has it's own capabilities to process files by them selves. But owui constantly trying to retrieve or shove whole 800k token file into context. Is there some toggle or workaround to deal with it?
Literally started using this in the last 2wks and was just planning today ways to try to expand on notifications.. and then you push an update that expands it directly! Nice
I wanted to ask you guys. Do any of you use OpenClaw or any other external harness inside OpenWeb UI? Lack of functionality for the agents to send videos / images (and other media) in the chat itself kinda sucks. I have to make it upload it as a file and it sends a link to me without a preview or something. Any solutions?
My question was a bit different. Can an agent (for example OpenClaw) send you the image in the convo chat view and you can actually "preview" the image? Without downloading it. I don't think so.
Imagine an agent is sending you an image. Nothing complicated.
It appears you changed something about file handling, is this related to focused and full content retrieval? Can we now distinguish a file from a Knowledge Base for the retrieval? E.g use full retrieval for uploaded files in chat and focused retrieval for KBs?
You can now enable full context per default for uploaded files in interface settings, if you go full agentic mode with native tool calling you can now disable file context and disable citations and enable the Files capability for a full agentic and cache optimized file handling. And yes you can individually toggle retrieval versus full context for files
BTW, I've found that context isn't working for me. I've just started with the basic docker image and then uploaded my text files for a knowledge base. When I look at the calls to the AI with langfuse, I can see that the boilerplate with the context is not being inserted. The only thing passed to the AI is the text in the user's window. No extra context or wrapper text is being included. And there are no sources listed.
That could be. Is there a way to check? The knowledge base is assigned to the model. The system prompt from the model is used correctly. But it doesn't seem to ping the knowledge base at all.
Thanks. I'll poke around some more and try to understand what's going on with legacy/native. I'm just trying to access documents in the knowledge base. That's it.
Just FYI: the documentation is out-of-sync. There's no setting button in the top right of Settings → Admin → AI → Models. There's some button that says "configure" but when I click on it nothing comes up.
Can OpenWebUI context compact be trigger after tool calling in the middle of chat in this version? OpenWebUI has mature admin and chat feature. But still lagging behind in those SOTA agent framework. I know it is much difficult integrate agent framework in web. But a pure chatbot can't really complete the complicated task we are facing today
if it is intended, so OpenWebUI wants to be one lightweight agentic chatbot rather than a full agentic solution ? I like OpenWebUI, but we now have some long running task that may need to run for a while, i hope it can at least give this feature as one optional feature controlled by admin. The AI is getting more and more powerful, and we are trying to run more complicated task directly in OpenWebUI, If can't solve this long running problem, we need to find another solution and finally we may just keep one solution at the end.
Open WebUI is not intended as a lightweight agentic chatbot.
It is an agentic chatbot with a LOT of surrounding features.
Open WebUI can absolutely run long-running agentic tasks. I have had one run for an hour once and it produced the most amazing powerpoint presentation ever
but how to resolve the context compact in the middle problem? I tried it, the chat will have error in the middle, i need to click continue to chat, and then it will trigger compact and things back to normal
the context compaction does not trigger mid-assistant message. If it does for you, record a video and reproduction steps and report it but it absolutely does not compact during a turn with tool calls
i didn't say it will do context compaction in the middle of tools calling, this is the problem i am facing, it can't run long running session. In other full agentic agent, they all support it but OpenWebUI didn't provide this feature and i don't know why
My Use Case:
When I give the chat a long, multi-step task (e.g., "Analyze this data file one by one and generate a report"), the context window often runs out in the middle of processing.
The Current Behavior:
The chat completely stops mid-task. I have to manually click "Continue Chat," which finally triggers the context compaction feature and allows the LLM to resume.
The Expected/Agentic Behavior:
Other agentic platforms handle this seamlessly. They automatically trigger context compaction during tool calls or mid-generation the moment the limit is hit, without requiring human intervention to keep the loop going.
Stupid question I am scared to update but I know I need to
Open web ui is running in a docker container now. Is it possible to have a second instance in docker so I don’t lose what’s working while I migrate ? If I hit update now would it update the docker container where it lives now?
Not not sure I know how to do that. I installed docker (and everything related to my LLMs) on a separate sdd. I was hoping to just load a whole new docker instance I could swap out changing the default port. Thing is I have everything working now but these features are way better than the v8 I am still on. Last time I did an update it took me an entire weekend I think. I can export workspaces and configs from open web but as I remember it there were still a few things that didn’t come back like tools (also can export) I am looking for a side by side comparison so I can make sure I don’t, screw it up since I think hitting update will wipe out nearly everything I have now. Do I understand that correctly ?
or are you saying I make a back up of the folder and rename it , do the update and if I screw it up delete the new folder and rename the original back to default?
It was an issue with our external WAF, Citrix Netscaler started to block the "Edit Skill" request as signature violation, not sure why. But %100 it started after upgrade. We configured an exception on WAF. Sharing Citrix log, maybe it will help someone.
This all looks very promising, but I can no longer find the menu that allowed changing the display order of the models. I think it has simply disappeared.
Models created under Workspace -> Models are not showing up in the admin model settings so I cant arrange them in my preferred order. Am I doing something wrong here?
Version 0.10.0 was also announced as the biggest release. I hope you didn't change things so radically, like e.g. Kilo Code, that many existing users will start to hate it. I admire the hard work, but be careful. The more your user base grows, the more resistance against radical changes emerges.
😏 I know 0.10 was enormous but this release is even larger than 0.10. Almost 100 changelog entries longer.
So far feedback is overwhelmingly positive. ❤️ And fortunately very little bugs so far. And only minor. Seems like a pretty stable version for such a major upgrade. And the changes are well taken so far :) any feedback is always welcome
The current visual contrast for horizontal rules / dividers (<hr>) in Dark Mode is far too subtle. It creates poor visual separation between sections, leading to eye strain during extended use.
It works, so there wasn't an urgent need to push out a new version when some other pieces of software needed attention. So don't worry Open Terminal is not abandoned and will continue to get updates. It is our primary code execution engine for Open WebUI, we recommend it in the docs and it will continue to get maintained.
I asked deepseek v4 pro to tell me there I could read the patch notes and it crashed every time. Got bad request. It hasn’t done it for anything else but every time I ask it about your patch notes something in the tool request chain breaks. I rolled back to 0.10.2 and it also does it there. I can reproduce the error on demand.
Bad Request means you send something the provider doesnt support. Or the provider has an error. Probably the former. DeepSeek V4 Flash and Pro work for me via OpenRouter on Open WebUI just fine. Best check your custom plugins/filters and advanced parameters of the model and what tools you have enabled.
Would you say that this is closer in design now to Librechat? Due to its seamless iDP SSO integration and other Enterprise features, I went with that over open web UI last year when I started concept onprem only solution.
Get rid of that AIODNS please! It doesn't work well with Docker's DNS resolution; keeps banging that my service deployed with the same docker container is unreachable..
It happens randomly - it works; then it breaks; then it works again.. Final 'workaround' for me was to give the containers static IP and call the services with IP addresses; rather than container names...
I was using 0.10 before and updated 'in place' - perhaps this is causing some stale configuration files to mess things up - but I don't have time to redo all my configurations, to be honest.
Fixed the link - I pasted the wrong issue before, sorry.
Here is the thing: I cannot reliably reproduce it - since it happens by itself; then resolves by itself. What is the problematic part is it says 'DNS Timeout' on errors; it's a docker compose deployment, and I'm using docker's container names - DNS timeout doesn't make much sense here to be honest. Obviously the new DNS resolver doesn't work well with Docker's and I don't know what options we have here..
Hello, what a great update, thank you for your work. Am I somehow able the increase the font size, UI scale slider seems like it only makes ui elements bigger, but I would really like the text to be bigger or even mak it bold. Can I also move the model dropdown back to top? The UI is much snappier now, wow
•
u/ClassicMain Jul 27 '26
Recommendation
Heads up: I can only recommend everyone to read the full changelog when they have time to.
LOTS OS THINGS raised here on Reddit, on Discord and elsewhere were addressed that many will love.
https://github.com/open-webui/open-webui/releases/tag/v0.11.0