mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
feat: Allow disabling prompt suggestions with an environment variable #5665
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#5665
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @yannxaver on GitHub (Jun 29, 2025).
Check Existing Issues
Problem Description
This is a follow-up to this comment: https://github.com/open-webui/open-webui/pull/13119#issuecomment-3015113559
It doesn't seem possible to disable prompt suggestions with an environment variable currently. Setting an empty array loads the hard-coded suggestions from the codebase. This is unfortunate because the hard-coded suggestions are in English, while OpenWebUI is available and being used in many different languages.
Desired Solution you'd like
Allow
DEFAULT_PROMPT_SUGGESTIONS=falseor introduceENABLE_PROMPT_SUGGESTIONSvariable to turn off the prompt suggestions.Alternatives Considered
No response
Additional Context
No response
@grigio commented on GitHub (Jun 29, 2025):
+1
@silentoplayz commented on GitHub (Jun 29, 2025):
I'm just stopping by to say I've requested for the same thing over on the Open WebUI Discord server. This feature request gets a
+1from me.Source: https://discord.com/channels/1170866489302188073/1242698289271410708/1380126138873151550
@git2212 commented on GitHub (Jun 29, 2025):
Why were prompt suggestions added in the first place?.... who's idea was this?... you either know what to ask an AI or probably prompt suggestions won't help...
OpenWebUI is trying to become everything to everybody and is accumulating pre-school teacher like qualities ... not a good aim, and features that add nothing but code bloat are being added in without proper consideration.
Bottom line, you can't compensate for people who are too lazy to learn the basics of prompt engineering iot speak to the AI properly. Like any other skills, you have to invest time and effort...
Take this feature out completely! No serious user of AI needs this!
@silentoplayz commented on GitHub (Jun 29, 2025):
The prompt suggestions are a helpful feature designed to assist users, especially those who are new to interacting with large language models. They provide a starting point for generating meaningful and effective prompts, which can save time and enhance the quality of interactions. While it's true that prompt engineering is a valuable skill, the suggestions serve as a guide to help users get started and gradually build their proficiency. The goal is to make the experience more accessible and inclusive for a wider range of users, not to replace the need for learning. If you find the suggestions unnecessary, you can always choose to ignore them or customize your experience to suit your preferences.
@git2212 commented on GitHub (Jun 30, 2025):
Well, as you can tell from the original poster the feature (specifically the disable part) is not working as expected... I can personally confirm spending almost an hour turning off the various features that just keep turning themselves back on (still working on figuring that one out) and also
a) are introduced without adequate mention in the changelog (yes I do read them),
b) not well documented (don't get me started on that lol)
c) not tested properly.
... but let's not loose sight of the fact that OpenWebUI has many great features... but it is also becoming bloated with more and more features that have nothing to do with being an AI tool (for anyone)... You can't compensate for people's lack of skills or unwillingness to put in the sweat equity with more and more features... I understand from your reply that that argument is not something you are going to accept, so let's just agree that we disagree.
While a lot of time is spent on "sexy" features the core issues (of which are many) are not addressed... the project lacks focus, period... decide what you want to be... who am I to complain right? ... you have it all figured out ;)
@i-iooi-i commented on GitHub (Jun 30, 2025):
This feature is great and it has helped me!
However, it may not be suitable for all model dialogs, and would prefer it to appear in the model's customization options.
@tjbck commented on GitHub (Jun 30, 2025):
You can disable already either from user settings or admin settings already.
@yannxaver commented on GitHub (Jun 30, 2025):
@tjbck How to do it using an environment variable? We want to initiate Open Web UI instances that are already preconfigured correctly.
@silentoplayz commented on GitHub (Jul 1, 2025):
This can be done for follow-up query generation, yes. But it seems like there's been a misunderstanding regarding the issue at hand. The original request of OP's issue post was to request for a direct way to disable
Default Prompt Suggestions, which are the suggested conversation starter prompts one would see displayed on aNew Chatpage if the user has default prompt suggestions added in their interface settings. Therefore, I believe this issue may have been prematurely closed.@silentoplayz commented on GitHub (Jul 1, 2025):
Perhaps there could be a toggle to enable/disable
Default Prompt Suggestionson a model level, but I believe it would best fit right where thePrompt Suggestionsarea lies on a model's edit page. Currently, one could only override theDefault Prompt Suggestionsfound in theInterfacesettings by setting prompt suggestions on a model level, but we can't disable those default prompt suggestions created in theInterfacesettings on a model-level currently, if desired.@silentoplayz commented on GitHub (Jul 1, 2025):
Default Prompt Suggestionscan be configured via the DEFAULT_PROMPT_SUGGESTIONS environment variable.@adamchurchwell commented on GitHub (Jul 14, 2025):
Customizing the default prompt suggestions using DEFAULT_PROMPT_SUGGESTIONS does not seem to work. They are a persistent config, set in config.json and written to the initial webui.db on start up. If anyone is able to figure this out, please let us know. I'm trying to avoid altering the base image to get this working.