[GH-ISSUE #16480] issue: Chat window level user valve values not persistent #33451

Closed
opened 2026-04-25 07:22:24 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @navilg on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16480

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.18

Ollama Version (if applicable)

No response

Operating System

Windows 11

Browser (if applicable)

Firefox

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

  1. I set custom values for function valves in a chat window (Say chat window 1)
  2. I move to another chat window (say chat window 2) and set some custom values for same function valves
  3. I come back to chat window 1
    4. I should see the the valve values which was set set in chat window 1 in step 1

Actual Behavior

  1. I set custom values for function valves in a chat window (Say chat window 1)
  2. I move to another chat window (say chat window 2) and set some custom values for same function valves
  3. I come back to chat window 1
    4. Valve value in chat window 1 is overridden by the value set in chat window 2

Steps to Reproduce

  1. Set custom values for a function valves in a chat window (Say chat window 1)
  2. Move to another chat window (say chat window 2) and set some custom values for same function valves
  3. Come back to chat window 1
  4. Check the valve value (It must have changed to value which was set in chat window 2)

Logs & Screenshots

NA

Additional Information

No response

Originally created by @navilg on GitHub (Aug 11, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16480 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.18 ### Ollama Version (if applicable) _No response_ ### Operating System Windows 11 ### Browser (if applicable) Firefox ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior 1. I set custom values for function valves in a chat window (Say chat window 1) 2. I move to another chat window (say chat window 2) and set some custom values for same function valves 3. I come back to chat window 1 **4. I should see the the valve values which was set set in chat window 1 in step 1** ### Actual Behavior 1. I set custom values for function valves in a chat window (Say chat window 1) 2. I move to another chat window (say chat window 2) and set some custom values for same function valves 3. I come back to chat window 1 **4. Valve value in chat window 1 is overridden by the value set in chat window 2** ### Steps to Reproduce 1. Set custom values for a function valves in a chat window (Say chat window 1) 2. Move to another chat window (say chat window 2) and set some custom values for same function valves 3. Come back to chat window 1 4. Check the valve value (It must have changed to value which was set in chat window 2) ### Logs & Screenshots NA ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 07:22:24 -05:00
Author
Owner

@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?

<!-- gh-comment-id:3174540870 --> @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?
Author
Owner

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

<!-- gh-comment-id:3174544902 --> @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.
Author
Owner

@spammenotinoz commented on GitHub (Aug 12, 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.

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

<!-- gh-comment-id:3177253981 --> @spammenotinoz commented on GitHub (Aug 12, 2025): > [@spammenotinoz](https://github.com/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. 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 -.
Author
Owner

@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 ?

<!-- gh-comment-id:3177452702 --> @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 ?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#33451