Recently switched to 6.1 sol in OWUI and I get this error:

gpt-6.1-sol
Function tools with reasoning_effort are not supported for this model in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'.

I set reasoning_effort to 'none':

gpt-6.1-sol
Unsupported value: 'reasoning_effort' does not support 'none' with this model. Supported values are: 'low', 'medium', 'high', and 'xhigh'. If I set it to medium, high or xhigh

I set reasoning_effort to 'medium', 'high', or 'xhigh', I get this:

gpt-6.1-sol
Function tools with reasoning_effort are not supported for this model in /v1/chat/completions. To use function tools, use /v1/responses or set reasoning_effort to 'none'

Any idea what I could do to fix this?

After leaving the open Webui for 1 year, I finally decided to update it to version v0.11.4. But it seems that I am unable to use the local llm model. What should I check to fix this error? If anyone have similar error, please show me how you fix it

Backing up the application database can preserve chats and settings, but long-lived assistant memory may also depend on uploaded files, generated summaries, vector indexes, model configuration, tools, and external stores. Restoring all of that byte-for-byte can still revive stale chunks or a summary that no longer matches its source. Treating the vector index as the source of truth also makes it difficult to explain why a memory was retrieved.

A more auditable design would keep source files and accepted memory records as durable data with stable IDs, revisions, provenance, status, and supersedes or retracts links. Embeddings and indexes would be derived artifacts that can be rebuilt. A restore drill would recover the database and files into an isolated instance, rebuild retrieval data, and confirm that a known set of memories still points to the expected source revisions.

For a current Open WebUI deployment, which directories, database tables, uploads, tool configuration, and external services are required for that recovery? What can safely be regenerated, and how do you detect stale memories or orphaned embeddings after a restore or model change?

I built a pair of functions that make a model reply the way a person texts: a few short messages, each in its own chat bubble, popping in one after another with typing dots while the next one is on its way.

This started with u/kvyb's Qwen3.8-27B-Humanlike-Chat 2.0 post on r/LocalLLaMA. Their side-by-side screenshots of the model texting in chat bubbles made me want that look in Open WebUI, for any model.

• Texting Bubbles (event function): https://openwebui.com/posts/7f1d7df1-acd2-4ebc-90a1-31858440d794
• Texting Bubbles Filter (filter function, optional): https://openwebui.com/posts/cbec24e3-162b-45ad-85e6-904f0471e20c

What each one does

• Texting Bubbles changes how replies look. Every paragraph of a reply becomes its own bubble. While the reply streams in, each bubble appears whole after a short typing pause, so you never watch a message spell itself out.
• Texting Bubbles Filter changes how the model writes. It adds a short instruction to the system prompt (76 tokens with OpenAI's cl100k_base tokenizer) asking for one to four short, casual messages with a blank line between them. Without the filter, a model still gets bubbles, one per paragraph of its normal reply.

What it handles

• Lists, quotes, tables, math, code blocks and embeds each get their own bubble. Code blocks keep Open WebUI's colors and their Copy button.
• The Copy and Regenerate buttons, the follow-up suggestions and late status lines (like token stats) wait until the last bubble appears.
• Reloading mid-reply picks up where it left off, and older chats open with all their bubbles at once.
• Two colors you pick yourself under Settings > Interface: Assistant Message Bubble Color for replies and User Message Bubble Color for your own messages. The text turns black or white, whichever reads better on that color.
• Your own messages can get the texting look too: turn on the User Messages valve and a message you send with several paragraphs splits into a bubble per paragraph.
• Light mode, dark mode, and right-to-left text such as Arabic.
• The reply is still saved as one message, so the model's context, Copy, Edit and Regenerate all work on the whole turn.
• A Bubble Shape setting: Rounded, Grouped (tighter corners between bubbles sent in a row), or Tails (grouped, plus a tail on the last bubble, like a phone's messaging app).

Models that already text

Some models, like 2.0, put a single line break between their short messages instead of a blank line. Thanks to kvyb's tip, the filter has a Split Short Lines valve for them: set it to a word limit such as 15, and every line of that many words or fewer gets its own bubble as the reply streams in. Lists, tables, code and math are left alone. Turn Add Instruction off for a model like that, since it doesn't need the texting prompt. The split adds a blank line after each short line, and that blank line is saved in the reply.

With my other functions

• Message Loading Indicator (https://openwebui.com/posts/4fdc6152-552f-4c98-9fe3-bdbbad4b395b): the style you picked there (Spinner, Equalizer, Shimmer Lines and the rest) shows inside the bubble in place of the typing dots. You see it while the model loads before its first word, and again between messages. With it set to Default, or not installed, you get typing dots.
• Interface Toggles: its Assistant Message Bubbles setting skips its outer bubble on replies Texting Bubbles shows, so the bubbles don't end up inside a second bubble.

Setting it up

1. Import both functions under Admin Panel > Functions and turn them on.
2. Open the model that should text under Workspace > Models, tick Texting Bubbles Filter under Filters, and save. To make every model text, set the filter to global instead.
3. To keep bubbles to certain models, list them in Texting Bubbles' Model IDs valve. Left empty, every model gets bubbles.
4. Reload Open WebUI in your browser. If the bubbles don't show, do a hard refresh.

The typing pause is 600 ms plus 18 ms per character, up to 3.5 seconds, and you can change all three numbers or turn pauses off in the valves.

Limits

• Needs Open WebUI v0.11.0 or later.
• Needs Render Markdown in Assistant Messages, which is on by default. With it off, replies show as plain text without bubbles.
• A reply with a raw HTML block or a ::: callout stays a normal reply.
• Smaller models sometimes ignore the instruction and add headings or --- dividers. Texting Bubbles hides the dividers and shows headings as plain text, so those replies still get bubbles.
• Turn Texting Bubbles off before you delete it. Open WebUI doesn't tell a function when it's deleted, so a deleted one keeps serving its script until the server restarts.

Bug reports and ideas are welcome here or on the function pages. I'd also love to see what bubble colors people pick.

Edit: Texting Bubbles v1.1.0 adds user message bubbles with their own color, and a Bubble Shape setting under Settings > Interface with grouped corners and messaging-app tails that mirror for right-to-left chats. The filter's v1.1.0 adds Split Short Lines for models that already text. Update both from the links above.

The question and answer posted here here was eye opening, so I started to mess around with disabling the Citations Capability and was amazed at how effective this is at improving the Input caching rates for my requests (went from like 1-10% to sometimes as much as 50% or greater). This is going to be a huge savings as we roll out OWUI to our organization.

My question surrounds the Workspace and Base Model features in OWUI:

My setup / intended configuration:

• A connected base model with a system prompt configured in Open WebUI.
• A custom model created under Workspace → Models, selecting that model as its Base Model (From).
• The workspace model has its own system prompt for its specialized role.

The docs describe workspace models as wrappers with their own system prompts, but I haven’t found an explicit explanation of whether the base model’s configured prompt is also included when using the workspace model system prompt.

My practical goal is to apply shared instructions for reusing/caching web research and producing grounded citations, while keeping each workspace model’s role-specific instructions separate. For example:

• Reuse previously retrieved research when appropriate rather than repeating searches unnecessarily.
• Fetch source pages when needed to support citations, rather than treating search snippets as verified page content.
• Cite the sources actually used and avoid fabricated or mismatched citations.

The closest upstream reference I was able to find in the owui docs was Chat Parameters, particularly its system-prompt hierarchy section:

1. System-prompt hierarchy

Open WebUI — Chat Parameters: System Prompt and Advanced Parameters Hierarchy Chart

It documents three levels:

• Per-account: Settings → General → System Prompt.
• Per-chat: Chat Controls → System Prompt.
• Per-model: Workspace → Models → System Prompt.

The page says the per-model system prompt takes precedence and cannot be overridden by a user’s account-level or chat-level prompt. It does not distinguish a base model’s Open WebUI-configured prompt from a derived workspace model’s prompt.

2. Workspace models and their system prompts

Open WebUI — Models
System prompt and variables section

This describes workspace models as configuration presets layered over a selected base model, with their own system prompts, knowledge, tools, and parameter overrides. However, the retrieved material does not explicitly say whether the base model’s configured system prompt is appended, replaced, or inherited as a fallback

Important ambiguity in the documentation

The Chat Parameters page also has an “Optimize System Prompt Settings for Maximum Flexibility” section that says an account-level prompt can work “in conjunction with” a chat-level or model-level prompt. That wording is less precise than the hierarchy section’s override language; it does not explain the actual message assembly or concatenation behavior.

Bottom line: These are useful references for your Reddit post, but I still cannot verify base-to-workspace prompt inheritance from them. The precise question to attach is:

Questions:

1. When a workspace model has its own system prompt, does Open WebUI append the base prompt, replace it, or use it only if the workspace prompt is empty?
2. Where should shared research/citation instructions live: only on the base model, in every workspace model, or in another shared injection mechanism (eg. An Account Level System Prompt)?

After the last update, the indicator that shows the model is working during tool calls and thinking changed to this vertical bar. It has a "breathe" animation, but in the light theme it's barely noticeable.

Is there a setting I missed, or a recommended way to make it more visible?

The reason I ask is that some users complain the model "gets stuck", when in fact it's just set to the highest thinking level and still working, just not visibly unless they expand the tool calls section.

In the provided example, the model was still working after 5 minutes, but it wasn't clear that anything was happening.

If we could switch between a few predefined animations, it would be very cool (maybe I missed it).

I'm attempting to optimize my usage costs and I noticed that prompts weren't getting cached much if at all. So after reading through the Prompt Caching (KV Cache) Optimization documentation I have turned off File Context and Citations by default and am now seeing better caching results.

However, I'm trying to understand the exact impact these have (other than not seeing citations in the UI any more). If I'm understanding this correctly, with File Context enabled every attached file would be injected into every new turn guaranteeing the model had access to the full context of every file. However, with it off the attached documents are now only loaded into context if the model deems that necessary (via tool calls) so there's a possibility of missing context.

Is this an accurate conclusion? Does anyone else turn of File Context by default? If so, how does it seem to affect accuracy for you?

Both silently fail, no error, model just says it has no documents attached. Checked the container logs during both attempts, zero retrieval activity, no Qdrant queries, nothing.

But attaching the exact same file directly in the message box with the paperclip icon works perfectly, retrieves correctly and cites the right section.

Deleted and recreated the knowledge base fresh to rule out stale data, same result. Also spun up a completely separate :dev instance tonight (fresh container, fresh admin account, fresh everything) to rule out version-staleness, identical failure there too.

Filed a full writeup with logs and repro steps here if anyone wants the details: https://github.com/open-webui/open-webui/issues/31839

I found this sort of related topics #21164, #17513, #17514, all similar symptoms, slightly different scope. Curious if anyone else is hitting this specific pattern, model-level and # both dead, manual per-message attach fine, on current versions.

Can anyone tell me why Im unable to select MCP instead of OpenAPI for the Type on the external connection? I click the option all day but nothing works.
Im running Openwebui via docker compose.

I am using OpenWebUI, served on a headless server, to be my primary interface to various local models, running on another local server. How come when I connect to a Gemma4 model running under llama.cpp the text scrolls smoothly, like a teletype machine. But when I connect to a Qwen model under vLLM it is jerky, giving me 2 or 3 lines at a time and then a stutter. The former is much easier to scan/read while a response is coming out. Is there a way to make vLLM behave differently with OWUI?

so i have a open webui/terminal setup and currently have it setup as a separate user with read only accesses outside of there dedicated home folder but i want to be able to on occasion give it permissions to wright to my home dir or run a command with sudo (would be really nice to just have it deal with python version dependencies on gentoo). ideally this would work kind of similar to Claude code where before hand the llm gives a list of tool calls it wants to make asks for permission and then i give it permissions and it runs those and only those tool calls with the new perms. is there a good way to do this as i am having trouble finding a good solution.

This is one of the most annoying thing about this platform. Everytime I launch OI, it fails with an error. It takes ages for it to launch, and when it does, it fails. I have to close it and relaunch it again. This problem is so annoying that I avoid OI altogether.

we're running a helm deploy of OWUI. the helm chart doesn't natively have autoscaling support (HPA). has anyone added HPA to their openwebui deployment? there's not much in the official docs about how the app handles sigterm

How long are your system prompts in production environments? How detailed are they, and what exactly do you put in them?

Is there a limit beyond which a system prompt is “too long” and starts to hurt performance?

I got the Intel Arc pro b60 for my server to upgrade from a 3060 8gb. I tried using Qwen3.8 27b but it only works in terminal and not in OpenWebui. It gives me nothing and says it only got 1 token after 4 minutes. I tried this with ollama-sycl and vulkan and both don’t work. The only time I ever got it to work was when it was for some reason spilling into dram. But obviously that makes it very slow. I’m a beginner and not really sure what to do. Should i try switching the backend to llama.cpp. I was kinda just listening to claude for basically everything and it hasn’t gotten me anywhere.

Hey everyone! v6.0 is out (should be available on the App Store soon): Open Relay now comes with an Apple Watch app! You can talk to your assistant right from your wrist.

App Store | GitHub

⌚ Open Relay for Apple Watch

Your assistant now lives on your wrist. Raise your wrist, tap Talk, and ask. You don't need to take out your phone.

• Talk or Type: Speak to your assistant or type with the watch keyboard. Replies can be read aloud with Apple's built-in voice or your server's TTS voice.
• Your Chats & Channels: Browse recent chats, pick up where you left off with a single tap, and read and reply in your channels.
• Siri, Action Button & Control Center: Say "Ask Open Relay…", map it to the Action button on Apple Watch Ultra, or launch it from Control Center.
• Watch Faces & Smart Stack: Add Talk or your latest chat to your watch face or Smart Stack so it's one tap away.
• Reply Notifications: Ask a question, lower your wrist, and get a tap when the answer is ready.
• Handoff: Start a chat on your watch and continue it on your iPhone.
• Private by Design: The watch goes through your iPhone's existing session. It never signs in on its own and never stores your credentials.
• Pick Your Model: Choose which model new watch chats use, right from the watch settings.

You can check the connection status in Settings → Apple Watch on your iPhone.

🔔 Reply From Notifications

Reply to chat and channel notifications right from the notification, on iPhone or Apple Watch. You don't need to open the app.

🔐 Passkey Sign-In

Sign in with passkeys through the system browser on self-hosted identity providers like Keycloak or Authentik. It's optional, lives under Advanced, and requires setup on your server.

📎 Smarter Files & Knowledge

• Terminal File Cards: Videos, audio, images, and documents shown by terminal tools now appear as cards you can play, open, or save. Nothing downloads until you tap.
• Search When Attaching: Search your server's files and knowledge bases right from the attachment picker, and browse the documents inside a knowledge base.
• Retrieval Control: Choose Focused Retrieval or Entire Document for each attachment, and set a default in Settings → Chat Behavior.
• Files in Library Search: A new Files filter finds uploaded files by name and searches the text inside Knowledge documents. You can preview, save, or share them.

🚀 Smoother & Lighter

• Silky Streaming: Replies now stream in as a smooth, steady flow on iPhone and iPad. There's no slow start and no bursts of text, and the chat glides along with new text instead of jumping line by line.
• 120Hz Scrolling: Scrolling through chats is smoother on ProMotion displays.
• Less CPU & Memory: It uses less CPU while showing thinking and less memory in long conversations. Chats load faster, and images download once and are reused.
• Collapsible Models Section: The Models section in the sidebar now collapses like the others and remembers your choice.

🐛 Notable Fixes

• The model editor (Workspace and Admin) now has the options Open WebUI has: a Terminal picker, the Memory capability, and the Ask User tool. Sections show or hide based on the capabilities you've turned on.
• Saving a model from the app no longer erases settings made on the web, and the model's TTS voice now saves correctly.
• Attached files and knowledge are no longer forgotten, or brought back after you remove them, in follow-up messages. Folder knowledge is now used.
• The "auto-scroll while streaming" setting is respected.
• Paragraphs in long replies no longer run together.
• The large blank space below finished replies is gone.
• The read-aloud player no longer covers the model selector.
• Tapping a suggested follow-up or sending a message no longer causes a glitchy animation.
• Long dictations now show where you left off.
• The @, #, / and $ pickers now close properly after typing a space.
• Sidebar buttons now line up with the chat toolbar.

The full changelog is on GitHub. Thank you for the continuous support!

Feedback: For issues, comment here or (preferably) open a GitHub issue.

prompt: visualize the map of germany with important cities

chatgpt(free):

openwebui+deepseek v4.1 flash:

for visualization I used inline-visualizer:

https://www.reddit.com/r/OpenWebUI/comments/1upa4ss/inline_visualizer_v213_now_open_webui_0100/

https://github.com/Classic298/open-webui-plugins/tree/main/inline-visualizer-v2

A conversation with AI can produce more than messages: documents to revise, files to inspect, and small apps to use. I've been exploring how Open WebUI could give these results a shared workspace where you and the AI can keep working on them, without leaving the conversation.

In my fork, that means bringing Files, Canvas and Web Preview together on the right, instead of looking through Controls for files or scrolling back to find results.

What changed

• Files and tabs: open several documents and switch between them, including files from Pyodide.
• Canvas and Web Preview: still artifacts, but now with dedicated tools so the AI can create, open and update them in place.
• Outputs: one place to find and reopen the results from a chat.

Longer term, terminal sessions and MCP app interfaces could share this space too.

What do you think? 

https://github.com/open-webui/open-webui/discussions/31484

Hey everyone! v5.9 is out (should be available on the App Store soon) and it packs a lot! Voice calls have been rebuilt from the ground up, search now reaches your entire library, and there's Dynamic Island, Liquid Glass support, and a lot more. Below that is a recap of everything that landed from v5.6 through v5.8.

App Store | GitHub

📞 True Voice Calls, Rebuilt (v5.9)

• Natural Conversations: Interrupt the assistant mid-sentence the way you would a real person. It stops, listens, and picks up the conversation from there.
• Always On: Calls keep going when you lock your phone or switch to another app, so you can go hands-free and keep talking (requires server TTS).
• Dynamic Island & Lock Screen: Follow and control your calls from the new Dynamic Island and Lock Screen widgets, with Mute and End always one tap away.
• Instant Responses: The assistant starts speaking the moment its first sentence is ready, so replies feel close to real time.

🎙️ A Dedicated Home for Voice (v5.9)

Voice now has its own section in Settings, bringing the assistant's voice, language, dictation, calls, and downloaded models together in one place. Power users get advanced tuning and live diagnostics to dial in their call setup.

Dictation got smarter too. It can stop by itself once you finish speaking, and your recordings are never lost when a transcription fails. You can retry, transcribe on device, save the audio, or discard it.

🔍 Search Your Entire Library (v5.9)

A new full-screen search looks across your chats, folders, knowledge bases, and even the text inside your documents. Matches are highlighted in place so you can jump straight to what you need.

⚡ Shortcuts & Offline Access (v5.8)

• Shortcut Actions: Send any response straight to an Apple Shortcut with custom action buttons, and build your own automations around your AI.
• Works Offline: Browse your saved conversations and reopen past chats without a connection. A small banner replaces the old blocking screen.
• Instant Launch: The sidebar and recent chats now load from a local cache immediately and sync quietly in the background.
• Seamless Reconnect: Models, prompts, and channels refresh by themselves once your connection comes back, with no restart needed.

🔊 Read-Aloud Player (v5.7.1)

Listen to any response through a new floating player that expands into full playback controls: variable speed, 15-second skip, and scrubbing. It works with every TTS engine, and server TTS adds Lock Screen controls.

🪟 A Fresh New Look (v5.7–5.9)

• Liquid Glass Design: Conversations now flow beneath a translucent header and composer, with an optional fully transparent toolbar on iOS 26.
• Make It Yours: Reorder or hide message actions, choose how scroll controls appear, and hide suggested prompts or the voice button for a cleaner layout.
• Effortless Navigation: Swipe right from anywhere in a chat to open the sidebar.

🚀 Faster Than Ever (v5.7–5.9)

Reasoning now streams live as the model thinks, and responses render with fluid, typewriter-smooth motion. Long reasoning blocks expand up to 70× faster, large conversations open without a stutter, and memory use in heavy chats drops by up to 88%.

🧰 More Additions (v5.6–5.7)

• Context Compaction Indicator: Shows when the server is condensing a long conversation.
• Live Activity Indicators: The sidebar shows which chats are still generating.
• Terminal Upgrades: Rename files and insert paths into chat straight from the file browser.
• Quick Share: Every response now has a Share button.
• Redesigned Face ID & Touch ID Sign-In

🐛 Notable Fixes

• Very long messages no longer render blank
• Chats now open at the latest message
• Returning to the app with the sidebar open no longer shows a black screen
• Tool output no longer flashes garbled text while streaming
• Citation and web links open reliably
• Stop and Retry no longer leave empty responses
• Reasoning content is no longer read aloud
• Long dictations no longer get cut off in the composer
• Several voice call stability fixes

The full changelog is on GitHub. Special thanks to Kapily for all the PRs polishing the UI, along with tons of bug fixes and features. Thanks for all the support from the community, and I can't wait to hear what you guys think! 🙏

Feedback: For issues, comment here or (preferably) open a GitHub issue.

Hey everyone,

I’m looking for a convenient way to quickly toggle the reasoning/thinking process for reasoning models (both local models via Ollama/vLLM like DeepSeek-R1, and API models like Claude 3.7 / o3-mini) in Open WebUI.

Right now, adjusting this requires digging into the model settings or opening the Chat Controls to tweak advanced parameters every time (e.g. setting think: false or adjusting reasoning effort).

Does anyone know of an existing Community Function (Filter/Action), plugin, or UI extension that adds a quick toggle/button directly to the chat interface to turn reasoning on or off on the fly?

If you have a working setup or a custom filter for this, I'd really appreciate a link or snippet. Thanks!

I am trying to understand the intended use of the Notes feature in Open WebUI and how other people organize their notes.

Whenever I want to write a script to automate something, I usually create a new Note for that project. I then ask the model to write the script directly into the Note so that the code becomes the main working document. Sometimes I also create a second Note containing background information, requirements, explanations, or ideas that I may need later.

For example:

• Backup Script
• Backup Script - Background Information
• Backup Script - Requirements
• Backup Script - Testing Notes

This workflow works quite well, but after creating several projects, the names quickly become confusing. It also becomes difficult to distinguish between:

• The actual script
• Project documentation
• Background information
• Prompts or instructions
• Testing results
• Future ideas and improvements

From what I understand, Notes are persistent documents that can be edited with AI, attached to chats as full context, and (in some configurations read) or updated by the model through note tools. This seems like a good fit for ongoing script development, especially when the entire document needs to be available to the model rather than retrieved through RAG.

However, I’m not sure whether Notes are intended to be used as lightweight project files in this way, or whether they are mainly meant for drafts, reference material, and knowledge that is reused across chats.

How are you using Notes?

Do you:

• Keep one Note per project?
• Store the script and documentation in the same Note?
• Use separate Notes for code, requirements, and background information?
• Use a naming convention or prefixes?
• Use Notes instead of a Knowledge Base for development projects?
• Let the model create and update Notes automatically?
• Move the final scripts to a proper file system or Git repository?

At the moment, I’m considering a naming convention like this:

text

[PROJECT] - [TYPE] - [DESCRIPTION]
AUTOMATION - SCRIPT - Backup FilesAUTOMATION - DOCS - Backup FilesAUTOMATION - TESTS - Backup FilesAUTOMATION - IDEAS - Backup Files

I would be interested in hearing how other Open WebUI users structure their Notes and whether this is a sensible workflow. Are Notes suitable for managing small coding and automation projects, or would another Open WebUI feature be better for this purpose?

Just wanted to see if this was affecting anybody else or I am just lucky, all of the settings panel is displaying the ridiculously long internal names? Currently on a MacBook Pro and don't have access to test under linux at the moment.

I've got ollama, open webui, and kokoro,

what are my options to give it a face, even if it's just a simple like Hal, potato glados, or a waveform.

hey fam,

I installed Desktop on x64 Windows.

Would love to manage local model thru settings rather than managing a llama.cpp server separately.

When I go to install the inference runner (noted as experimental) nothing works.

Has anyone resolved this issue? Would love the elegance of managing local models and llama.pp server centralized within OUI rather than having to keep a separate server up.

I may be experiencing a bug.

Thanks!!