I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.6.40
Ollama Version (if applicable)
0.13.0
Operating System
Debian 12
Browser (if applicable)
All
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
Usage settings for given model remains as set regardless of model changes
Actual Behavior
usage model setting becomes unticked when model is changed
Steps to Reproduce
Create custom model in Workspace > Models
Tick "usage" for the model
Save it and refresh the page to confirm it is still ticked
Change the model to some other (For me it happened when changing it from o3 to gpt-5 for example)
Notice that the "usage" becomes unticked
Logs & Screenshots
Additional Information
No response
Originally created by @YetheSamartaka on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19549
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.6.40
### Ollama Version (if applicable)
0.13.0
### Operating System
Debian 12
### Browser (if applicable)
All
### 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
Usage settings for given model remains as set regardless of model changes
### Actual Behavior
usage model setting becomes unticked when model is changed
### Steps to Reproduce
1. Create custom model in Workspace > Models
2. Tick "usage" for the model
3. Save it and refresh the page to confirm it is still ticked
4. Change the model to some other (For me it happened when changing it from o3 to gpt-5 for example)
5. Notice that the "usage" becomes unticked
### Logs & Screenshots
<img width="1014" height="123" alt="Image" src="https://github.com/user-attachments/assets/4c66fc16-883f-4913-a4d9-1a526ea23f25" />
### Additional Information
_No response_
This issue has been reported internally as well and is on our radar. I can confirm that I am also able to reproduce this issue on the latest dev commit at the time of me making this comment.
<!-- gh-comment-id:3588262304 -->
@silentoplayz commented on GitHub (Nov 28, 2025):
This issue has been reported internally as well and is on our radar. I can confirm that I am also able to reproduce this issue on the latest `dev` commit at the time of me making this comment.
Yes, this issue is still reproducible on the latest dev.
<!-- gh-comment-id:3652472788 -->
@silentoplayz commented on GitHub (Dec 15, 2025):
> [@silentoplayz](https://github.com/silentoplayz) can you still reproduce?
Yes, this issue is still reproducible on the latest dev.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @YetheSamartaka on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19549
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.40
Ollama Version (if applicable)
0.13.0
Operating System
Debian 12
Browser (if applicable)
All
Confirmation
README.md.Expected Behavior
Usage settings for given model remains as set regardless of model changes
Actual Behavior
usage model setting becomes unticked when model is changed
Steps to Reproduce
Logs & Screenshots
Additional Information
No response
@silentoplayz commented on GitHub (Nov 28, 2025):
This issue has been reported internally as well and is on our radar. I can confirm that I am also able to reproduce this issue on the latest
devcommit at the time of me making this comment.@Classic298 commented on GitHub (Dec 14, 2025):
@silentoplayz can you still reproduce?
@silentoplayz commented on GitHub (Dec 15, 2025):
Yes, this issue is still reproducible on the latest dev.
@Classic298 commented on GitHub (Dec 21, 2025):
https://github.com/open-webui/open-webui/pull/19729/changes/6993b0b40b10af8cdbe6626702cc94080fff9e22..7e4848e10bb155c1ec679fbdd3b570709d078f39