mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #16480] issue: Chat window level user valve values not persistent #17922
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 @navilg on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16480
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.18
Ollama Version (if applicable)
No response
Operating System
Windows 11
Browser (if applicable)
Firefox
Confirmation
README.md.Expected Behavior
4. I should see the the valve values which was set set in chat window 1 in step 1
Actual Behavior
4. Valve value in chat window 1 is overridden by the value set in chat window 2
Steps to Reproduce
Logs & Screenshots
NA
Additional Information
No response
@spammenotinoz commented on GitHub (Aug 11, 2025):
For myself non-admin can lo longer modify settings or chat controls. (cleared cookies and cache) is this the same or separate issue?
@tjbck commented on GitHub (Aug 11, 2025):
@spammenotinoz sounds like a separate issue
user valves are overridden as soon as you edit the values, if you refresh the page you'll the displayed values are also updated as well.
@spammenotinoz commented on GitHub (Aug 12, 2025):
Thanks for the reply, I won't raise a bug as the issue is caused by a Browser Extension "Malwarebytes", just triggered by the latest Open-Webui. Strange though it impacts standard users only. I've done numerous tests, and def' the BrowserGuard Feature of Malwarebytes. Can't complain too much, it protected me from the fake openwebui.com site, you know the one with the -.
@navilg commented on GitHub (Aug 12, 2025):
@tjbck is this expected behaviour ?
If yes, then I think there is no use of providing option to set userValve values in chat level. Instead, It should have been somewhere in workspace or settings.
Because if we set userValve at chat level, it implies that these values are scoped that particular chat and then should not get overridden if the same valve's values are updated in some other chat. Dont you think ?