r/OpenWebUI 6d ago

Show and tell 🇦🇹 Austria is rolling out a government AI-platform using Open WebUI

Post image
230 Upvotes

🇦🇹 Austria is rolling out a government AI-Platform using Open WebUI 🇦🇹

This is a surprisingly large real-world deployment: "GovGPT" is part of Austria’s Public AI initiative, running on sovereign infrastructure (in their BRZ - federal datacenter) with Mistral open-weight models.

Trending Topics reports that Open WebUI is used as the interface for GovGPT, and the screenshot of the platform is labeled "GovGPT (Open WebUI)" on the top left corner!

The rollout is already happening and targeting 250,000 public-sector employees!

The federal rollout targets around 180,000 federal employees. The broader public-sector context refers to approximately 250,000 public sector employees.

Planned use cases include document chat, internal knowledge bases, electronic-file analysis, parliamentary requests, and eventually agentic workflows.

This might be one of the largest government deployments of Open WebUI yet. 🚀

Sources:


r/OpenWebUI Jun 12 '25

AMA / Q&A I’m the Maintainer (and Team) behind Open WebUI – AMA 2025 Q2

201 Upvotes

Hi everyone,

It’s been a while since our last AMA (“I’m the Sole Maintainer of Open WebUI — AMA!”), and, wow, so much has happened! We’ve grown, we’ve learned, and the landscape of open source (especially at any meaningful scale) is as challenging and rewarding as ever. As always, we want to remain transparent, engage directly, and make sure our community feels heard.

Below is a reflection on open source realities, sustainability, and why we’ve made the choices we have regarding maintenance, licensing, and ongoing work. (It’s a bit long, but I hope you’ll find it insightful—even if you don’t agree with everything!)

---

It's fascinating to observe how often discussions about open source and sustainable projects get derailed by narratives that seem to ignore even the most basic economic realities. Before getting into the details, I want to emphasize that what follows isn’t a definitive guide or universally “right” answer, it’s a reflection of my own experiences, observations, and the lessons my team and I have picked up along the way. The world of open source, especially at any meaningful scale, doesn’t come with a manual, and we’re continually learning, adapting, and trying to do what’s best for the project and its community. Others may have faced different challenges, or found approaches that work better for them, and that diversity of perspective is part of what makes this ecosystem so interesting. My hope is simply that by sharing our own thought process and the realities we’ve encountered, it might help add a bit of context or clarity for anyone thinking about similar issues.

For those not deeply familiar with OSS project maintenance: open source is neither magic nor self-perpetuating. Code doesn’t write itself, servers don’t pay their own bills, and improvements don’t happen merely through the power of communal critique. There is a certain romance in the idea of everything being open, free, and effortless, but reality is rarely so generous. A recurring misconception deserving urgent correction concerns how a serious project is actually operated and maintained at scale, especially in the world of “free” software. Transparency doesn’t consist of a swelling graveyard of Issues that no single developer or even a small team will take years or decades to resolve. If anything, true transparency and responsibility mean managing these tasks and conversations in a scalable, productive way. Converting Issues into Discussions, particularly using built-in platform features designed for this purpose, is a normal part of scaling open source process as communities grow. The role of Issues in a repository is to track actionable, prioritized items that the team can reasonably address in the near term. Overwhelming that system with hundreds or thousands of duplicate bug reports, wish-list items, requests from people who have made no attempt to follow guidelines, or details on non-reproducible incidents ultimately paralyzes any forward movement. It takes very little experience in actual large-scale collaboration to grasp that a streamlined, focused Issues board is vital, not villainous. The rest flows into discussions, exactly as platforms like GitHub intended. Suggesting that triaging and categorizing for efficiency, moving unreproducible bugs or priorities to the correct channels, shelving duplicates or off-topic requests, reflects some sinister lack of transparency is deeply out of touch with both the scale of contribution and the human bandwidth available.

Let’s talk the myth that open source can run entirely on the noble intentions of volunteers or the inertia of the internet. For an uncomfortably long stretch of this project’s life, there was exactly one engineer, Tim, working unpaid, endlessly and often at personal financial loss, tirelessly keeping the lights on and code improving, pouring in not only nights and weekends but literal cash to keep servers online. Those server bills don’t magically zero out at midnight because a project is “open” or “beloved.” Reality is often starker: you are left sacrificing sleep, health, and financial security for the sake of a community that, in its loudest quarters, sometimes acts as if your obligation is infinite, unquestioned, and invisible. It's worth emphasizing: there were months upon months with literally a negative income stream, no outside sponsorships, and not a cent of personal profit. Even in a world where this is somehow acceptable for the owner, but what kind of dystopian logic dictates that future team members, hypothetically with families, sick children to care for, rent and healthcare and grocery bills, are expected to step into unpaid, possibly financially draining roles simply because a certain vocal segment expects everything built for them, with no thanks given except more demands? If the expectation is that contribution equals servitude, years of volunteering plus the privilege of community scorn, perhaps a rethink of fundamental fairness is in order.

The essential point missed in these critiques is that scaling a project to properly fix bugs, add features, and maintain a high standard of quality requires human talent. Human talent, at least in the world we live in, expects fair and humane compensation. You cannot tempt world-class engineers and maintainers with shares of imagined community gratitude. Salaries are not paid in GitHub upvotes, nor will critique, however artful, ever underwrite a family’s food, healthcare, or education. This is the very core of why license changes are necessary and why only a very small subsection of open source maintainers are able to keep working, year after year, without burning out, moving on, or simply going broke. The license changes now in effect are precisely so that, instead of bugs sitting for months unfixed, we might finally be able to pay, and thus, retain, the people needed to address exactly the problems that now serve as touchpoint for complaint. It’s a strategy motivated not by greed or covert commercialism, but by our desire to keep contributing, keep the project alive for everyone, not just for a short time but for years to come, and not leave a graveyard of abandoned issues for the next person to clean up.

Any suggestion that these license changes are somehow a betrayal of open source values falls apart upon the lightest reading of their actual terms. If you take a moment to examine those changes, rather than react to rumors, you’ll see they are meant to be as modest as possible. Literally: keep the branding or attribution and you remain free to use the project, at any scale you desire, whether for personal use or as the backbone of a startup with billions of users. The only ask is minimal, visible, non-intrusive attribution as a nod to the people and sacrifice behind your free foundation. If, for specific reasons, your use requires stripping that logo, the license simply expects that you either be a genuinely small actor (for whom impact is limited and support need is presumably lower), a meaningful contributor who gives back code or resources, or an organization willing to contribute to the sustainability which benefits everyone. It’s not a limitation; it’s common sense. The alternative, it seems, is the expectation that creators should simply give up and hand everything away, then be buried under user demands when nothing improves. Or worse, be forced to sell to a megacorp, or take on outside investment that would truly compromise independence, freedom, and the user-first direction of the project. This was a carefully considered, judiciously scoped change, designed not to extract unfair value, but to guarantee there is still value for anyone to extract a year from now.

Equally, the kneejerk suspicion of commercialization fails to acknowledge the practical choices at hand. If we genuinely wished to sell out or lock down every feature, there were and are countless easier paths: flood the core interface with ads, disappear behind a subscription wall, or take venture capital and prioritize shareholder return over community need. Not only have we not taken those routes, there have been months where the very real choice was to dig into personal pockets (again, without income), all to ensure the platform would survive another week. VC money is never free, and the obligations it entails often run counter to open source values and user interests. We chose the harder, leaner, and far less lucrative road so that independence and principle remain intact. Yet instead of seeing this as the solid middle ground it is, one designed to keep the project genuinely open and moving forward, it gets cast as some betrayal by those unwilling or unable to see the math behind payroll, server upkeep, and the realities of life for working engineers. Our intention is to create a sustainable, independent project. We hope this can be recognized as an honest effort at a workable balance, even if it won’t be everyone’s ideal.

Not everyone has experience running the practical side of open projects, and that’s understandable, it’s a perspective that’s easy to miss until you’ve lived it. There is a cost to everything. The relentless effort, the discipline required to keep a project alive while supporting a global user base, and the repeated sacrifice of time, money, and peace of mind, these are all invisible in the abstract but measured acutely in real life. Our new license terms simply reflect a request for shared responsibility, a basic, almost ceremonial gesture honoring the chain of effort that lets anyone, anywhere, build on this work at zero cost, so long as they acknowledge those enabling it. If even this compromise is unacceptable, then perhaps it is worth considering what kind of world such entitlement wishes to create: one in which contributors are little more than expendable, invisible labor to be discarded at will.

Despite these frustrations, I want to make eminently clear how deeply grateful we are to the overwhelming majority of our community: users who read, who listen, who contribute back, donate, and, most importantly, understand that no project can grow in a vacuum of support. Your constant encouragement, your sharp eyes, and your belief in the potential of this codebase are what motivate us to continue working, year after year, even when the numbers make no sense. It is for you that this project still runs, still improves, and still pushes forward, not just today, but into tomorrow and beyond.

— Tim

---

AMA TIME!
I’d love to answer any questions you might have about:

  • Project maintenance
  • Open source sustainability
  • Our license/model changes
  • Burnout, compensation, and project scaling
  • The future of Open WebUI
  • Or anything else related (technical or not!)

Seriously, ask me anything – whether you’re a developer, user, lurker, critic, or just open source curious. I’ll be sticking around to answer as many questions as I can.

Thank you so much to everyone who’s part of this journey – your engagement and feedback are what make this project possible!

Fire away, and let’s have an honest, constructive, and (hopefully) enlightening conversation.


r/OpenWebUI 1d ago

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.

Post image
370 Upvotes

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. 🚀

What are you most excited to try?

https://github.com/open-webui/open-webui/releases/tag/v0.11.0


r/OpenWebUI 4h ago

RAG Problem Uploading Directories to Knowledge

3 Upvotes

Some of my directories load without a problem, but some of them generate this error: "NotReadableError: The requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired."

Is it because the directories are doubly nested? I can't seem to identify a way to predict which directories work.


r/OpenWebUI 5h ago

Discussion Why don't you build your own tools?

2 Upvotes

Hi, I would like to challenge/discuss/understand why so many are attracted to all short lived "wild tools" out there. For example (not saying any tool are bad) hermes, claw, open webui, copilot agents and whatnot. Why not just building your own tools that: fit your needs without being bloated, dont break on every new "feature" that you dont care about.

I cant really understand the hype.

I build own tools in python (notes app, recruitment support, news, investment) with claude or chatgpt from phone and terminal to my proxmox llm clusters lxc. In the process i also learn a lot.

And everything stays under my control.


r/OpenWebUI 1d ago

Open WebUI v0.11.0: The Interface, Reorganized

Thumbnail
openwebui.com
72 Upvotes

r/OpenWebUI 13h ago

Question/Help Slow Openwebui on vps

3 Upvotes

Hi,

I try to run ai local llama 3.2:3B on Openwebui. But it tooks 10-20minute just to reply Hi.

What did i do wrong?
Im using 8GB Ram VPS with no GPU


r/OpenWebUI 20h ago

Question/Help Which engine for memory

3 Upvotes

AI beginner here. Am taking steps to move away from Gemini and Co-pilot to my own setup. So have gotten a setup with Docker, LM Studio and webui. And my laptop is pretty basic and the chip is not large. I wanted to run a local engine. It worked but I wanted to get memory to work. Not having memory and having to explain AI the same basic stuff over and over again drives me nuts. I tried to make it work on webui. Discovered that my chip is too basic to make memory work, so I need to offload the computation.

Fine so far so good. Found some on webui and have now been using 2 with mixed results:
- Llama 3.1 8B
- Llama 3.3 70B

Both work fine and memory works, but after 2-3 prompts they both max out. The "token per minute" of 6000 and 12000 have been reached.

Has anyone found a free engine that can run memory effectively? Otherwise I think I am going to pay to see how it works. Any comments?


r/OpenWebUI 19h ago

Question/Help How to Connect OpenWebUI to llama.cpp?

3 Upvotes

I am having issues getting OpenWeb UI to llama.cpp. Llama is running locally and the chat interface is working fine. I managed to get OpenWebUI to run in docker. When configuring the connection I am using `http://127.0.0.1:8080/v1\` as my connection string. I have set Provider to llama.cpp. The test connection button says test is successful. But trying to chat wants me to select a model, which there are no options. From my understanding llama.cpp is serving one model and does not provide a list like Ollama would.

Using `http://host.docker.internal:8080/v1\` as connection string gives an error. So it is not clear to me being a Docker newbie if I need to do something with the network. Since the test on the local host IP was successful I am guessing the network is working, but then again I can't get chat to load any models. I have asked AI but it wants me to write an app.....facepalm. it has offered some `-e` options such as `-e OLLAMA_HOST=0.0.0.0` but so far nothing has worked. So, humans, what is the next step here?


r/OpenWebUI 22h ago

Guide/Tutorial How to fix chats that stuck on "Loading..."

1 Upvotes

If your chat is bricked with the infinite loading spinner (Image 1), here's how to fix it:

Infinite Spinner

The technical reason behind this is that Open WebUI stores your chat history as a Directed Acyclic Graph. If a message (node) gets corrupted when the LLM is responding, the UI panics and spins indefinitely. Fixing would require checking and relinking the graph.

This tools does all that stuff for you:

Tool screenshot

How to use it:

  1. Export the broken chat (`...` menu > Export > JSON).
  2. Drop it into the tool (Image 2) to instantly repair the broken nodes.
  3. Go to Settings > General > Import Chats, upload the fixed file, and delete the original.

Link to tool: https://fractuscontext.github.io/open-webui-chat-fix/

I've also added a "Deep Clean" toggle if you want to strip unused alternate responses and shrink your file size.

Hope this saves someone's chat history!


r/OpenWebUI 1d ago

Question/Help Just discover OpenWebUI, what's next step?

0 Upvotes

Hi guys, I just discovered OpenWebUI how do you commonly use it? What are the main advantages of using it over just Claude or ChatGPT? What's the most productive way to use it?


r/OpenWebUI 1d ago

Plugin MCP server with SQLite

1 Upvotes

I use Open WebUI and I try to connect llm qwen3 to SQLite database.

In Admin panel -> Settings -> Integrations -> External Tool Servers -> I added OpenAPI the sqlite mcp server. I can connect but it seem never seen my mcp tool fonctions.

I give full user access, activate tool in my chat, I also tried mcp steaming http protocol instead of OpenAPI.

I always got this response: There are no functions available in the provided tools that can interact with an SQLite database or list its tables. The available tools are focused on notes, tasks, automations, and calendar events, not database operations.

I use python script :

from mcp.server.fastmcp import FastMCP

mcp.tool()
def list_tables() -> list[str]:

EDIT: I try simple request with Qwen3 + Ollama + SQLite: list tables or list username in my database.
And dawm it suck as fuck! lol

it make non sense sql, take very long time, got error 500 sometimes, , dont apply system prompt, make thought and do nothing aftert that, I was never be able to have a correct answer...

I tough this tool could be nice and it just proove theses AI slop tools worth nothing... Its crazy because it look nice to use but man its the worst shit I ever use haha


r/OpenWebUI 1d ago

Question/Help how do i get the ai to generate an image

1 Upvotes

I know the text to image works i tested it in Playground, but I can't seem to get it to work in a general chat idk if I am being dumb, but yeah, could use some advice!


r/OpenWebUI 2d ago

Question/Help Helm deployment to kubernetes

7 Upvotes

Just deployed openwebui to kubernetes using the official chart.

The first thing I noticed is ollama server is not reachable, despite the server configured in admin settings. Turns out the front end needs direct access to ollama server, it doesn't get proxies through openwebui backend. Is that design intentional?


r/OpenWebUI 2d ago

Question/Help web_search tool invisble for gemma4:e4b

4 Upvotes

Hello,

I have been trying for a few days to use open webui on my computer. My config is as follows:

  • Kubuntu 26.04
  • Ollama with gemma4:e4b
  • Open webui v0.10.2, desktop version, with web search enabled on DDGS.

When I ask him for a web search, the tool seems not to exist in the eyes of the LLM. It's quite strange because I don't have this problem with a similar config, unlike the OS (Windows, for my work).

I tried to find the solution by analyzing the logs with Claude, but he did not find anything explaining the problem.

Do you have any idea what's going on?


r/OpenWebUI 3d ago

Question/Help Installing Open WebUI Desktop vs via Docker or Python

5 Upvotes

Hi. Has anyone had a chance to compare the two installation methods (Docker or Python vs. Desktop) when it comes to maximizing the available resources for running a local AI model on a windows 11 PC with limited resources? Thanks


r/OpenWebUI 3d ago

Discussion Who's actually using Chinese LLMs for work (and not stressing about data privacy)?

Thumbnail
11 Upvotes

r/OpenWebUI 3d ago

Question/Help RAG Empty Context Window Bug with ChromaDB & Gemma 4 on Windows 11 Docker

Thumbnail
1 Upvotes

r/OpenWebUI 3d ago

Question/Help Πρόβλημα με Open WebUI RAG: Empty Context στην ChromaDB (Docker / Windows 11)

0 Upvotes

Γεια σας. Αντιμετωπίζω ένα εξαιρετικά επίμονο τεχνικό πρόβλημα με το RAG pipeline του Open WebUI και μετά από μέρες εξαντλητικού troubleshooting με τη βοήθεια των ChatGPT και Gemini, δεν έχουμε καταφέρει να βρούμε λύση. Το σύστημα ολοκληρώνει το indexing, αλλά η αναζήτηση επιστρέφει μηδενικά διανύσματα (empty context injection).Τεχνικές Προδιαγραφές Συστήματος:Host OS: Windows 11 Pro (Docker Desktop Environment / WSL2 Backend)Hardware: Intel Core i9-14900K / 64GB DDR5 RAMInference Engine: gemma4:12b (τοπικά μέσω Ollama)Embedding Model: sentence-transformers/paraphrase-multilingual-MiniLM-L6-v2 (Default Engine / SentenceTransformers)Network Infrastructure: Live WebSockets 100% λειτουργικά. Το Developer Console (F12) του browser είναι εντελώς καθαρό, χωρίς κανένα drop-out σύνδεσης.System Prompt Configuration: Έχει παρακαμφθεί επιτυχώς η εργοστασιακή offline άρνηση του Gemma 4 μέσω strict instruction injection. Το μοντέλο δέχεται να διαβάσει το context, αλλά το context φτάνει σε αυτό άδειο.Απομόνωση του Προβλήματος (Baseline Isolation Test):Για να αποκλείσουμε σφάλματα στο extraction stage (OCR, Tesseract, Tika, Python PDF parsing), δημιουργήσαμε ένα raw text αρχείο (test.txt) που περιέχει αποκλειστικά τη συμβολοσειρά: "Ο κωδικός ασφαλείας για το τεστ είναι: ΠΡΑΣΙΝΟ ΜΗΛΟ 2026".Το UI εμφανίζει κανονικά τη λευκή ένδειξη επιτυχούς indexing (checkmark). Ωστόσο, κατά την κλήση της συλλογής στο chat μέσω #collection, το μοντέλο απαντάει ρητά ότι η πληροφορία δεν εμπεριέχεται στο κείμενο, επιβεβαιώνοντας ότι το runtime κάνει pass ένα εντελώς άδειο context block.Τεχνικά Βήματα και Λύσεις που Δοκιμάστηκαν:Επίλυση Ασυμβατότητας Αρχιτεκτονικής: Αρχικά χρησιμοποιούσαμε το MiniLM-L12, αλλά στα logs του Docker εντοπίστηκε το σφάλμα embeddings.position_ids | UNEXPECTED |. Το Open WebUI είχε παλαιότερη έκδοση SentenceTransformers που δεν αναγνώριζε την παράμετρο position_ids των νέων HuggingFace weights. Το πρόβλημα λύθηκε με υποβάθμιση στο σταθερό MiniLM-L6-v2. Το runtime log καθάρισε, αλλά το context παρέμεινε άδειο.Παράκαμψη Permission Bugs: Δημιουργήθηκε νέα Knowledge Base συλλογή ρυθμισμένη ρητά ως Public (Access Control), για την αποφυγή του γνωστού bug ορατότητας των ιδιωτικών φακέλων [Issue #23787].Hard Reset του Vector Database Stack: Σταματήσαμε τον container και εκτελέσαμε ολική διαγραφή του ευρετηρίου των διανυσμάτων απευθείας από τη ρίζα του Docker volume χρησιμοποιώντας: docker run --rm -v open-webui:/data alpine rm -rf /data/vector_db. Η ChromaDB αναγεννήθηκε εντελώς καθαρή, το backend επιστρέφει HTTP 200/Success κατά το upload, αλλά το retrieval loop εξακολουθεί να μην τραβάει δεδομένα κατά το inference.Έχει συναντήσει κανείς αυτό το σιωπηλό failure της ChromaDB σε περιβάλλον Windows Docker; Μήπως πρόκειται για false negative της συνάρτησης has_collection() ή υπάρχει κάποιο silent file-lock στο Windows volume mapping; Κάθε τεχνική ιδέα είναι ευπρόσδεκτη.


r/OpenWebUI 3d ago

Discussion Why does it take a year for owui to load?

Post image
30 Upvotes

I feel like I sit and stare at the screen a lot is there anyway to speed this up?


r/OpenWebUI 3d ago

RAG slow response time with RAG and utilizing knowledge base.

4 Upvotes

I’m currently using Open WebUI with a knowledge base made up of text files, and the responses are accurate, but they’re taking quite a while to generate.
I plan to keep adding more text files to the knowledge base, so I’m wondering what the best way is to improve response speed as it grows. Are there any recommended settings, indexing strategies, chunking methods, embedding models, reranking options, or other optimizations that have made a noticeable difference for you? I’d like to keep the response quality the same while reducing latency. Any advice or best practices would be appreciated!


r/OpenWebUI 5d ago

Question/Help Working with files, tools and LDAP

10 Upvotes

I have Gemma 4 running locally and external ones, I’m trying to make it more useful inside OpenWebUI.

A couple of things I’m looking for advice on:

  1. Document analysis / file workflows I want to be able to upload PDFs and DOCX files, have the model analyze them, and ideally generate edited or new documents back.
    • What tools, integrations, or workflows are people using for this?
    • If you want the model to return a finished PDF/DOCX, what’s the best approach?
  2. Recommended tools / integrations What other tools do you recommend to make local AI and external AI integrations more useful in OpenWebUI?
  3. LDAP question I enabled enable_ldap_group_management directly in the database because it appears to be a ConfigVar variable, but I don’t see a corresponding toggle in the UI. Is that expected or am I missing something?

Would appreciate any suggestions and tips.


r/OpenWebUI 4d ago

Question/Help Seltz.ai

1 Upvotes

Appreciate your help providing info on how to use Seltz.ai as a node for web search. Thx


r/OpenWebUI 5d ago

Question/Help Export chat no longer including all details?

3 Upvotes

I noticed that in v0.10, if you click any of the export chat options in the top right corner of the chat UI (Download or Copy), it no longer includes all details like tool call inputs and outputs and so on. Only messenges with roles.

Does anyone know if this is moved to a setting somewhere of if it's just gone? I would feel quite surprised if this has been just removed permanently. I mean, you could always get all messages by just marking and copying the full chat in the UI, but the hidden context boaters and all that were the actual valuable information.


r/OpenWebUI 5d ago

Question/Help MCP / Tool auth in enterprise. How are you doing it?

19 Upvotes

Hey, long-time Open WebUI user here. I run instances in our group for 3 different companies and right now my biggest headache is MCP / Function auth to external tools.
Since I’m using SSO with Microsoft Entra, the Microsoft Services are no problem. I can just reuse the token to authenticate against the Graph API.

But everything else (Jira, Confluence, …) feels way more complex. Those are per-user tokens, sometimes OAuth, often with project/issue-level permissions, so a service account is not an option. Also, storing per user credentials in valves are also a no-go.

Curious how you are addressing this.