I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
Currently when the backend model changes (such as if you use OpenAI compatible) the models under workspace/models do not default to the new model. Instead, the model becomes unset and you have to manually set the model. This is very painful to keep updating, especially when you have dozens if not outright hundreds of models.
In addition it confuses the end user as well...
Desired Solution you'd like
When the backend model changes and is no longer available, instead of workspace/models defaulting to unset they instead default to the current active model (the new model).
This could either be completely automated or a global setting/variable in the models section of the admin menu that can be updated manually.
Alternatives Considered
No response
Additional Context
This would solve a lot of grief (for myself, having to update 200+ models. And for my end users, who don't understand what's going on).
Originally created by @frenzybiscuit on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24261
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
Currently when the backend model changes (such as if you use OpenAI compatible) the models under workspace/models do not default to the new model. Instead, the model becomes unset and you have to manually set the model. This is very painful to keep updating, especially when you have dozens if not outright hundreds of models.
In addition it confuses the end user as well...
### Desired Solution you'd like
When the backend model changes and is no longer available, instead of workspace/models defaulting to unset they instead default to the current active model (the new model).
This could either be completely automated or a global setting/variable in the models section of the admin menu that can be updated manually.
### Alternatives Considered
_No response_
### Additional Context
This would solve a lot of grief (for myself, having to update 200+ models. And for my end users, who don't understand what's going on).
@frenzybiscuit commented on GitHub (Apr 30, 2026):
Note that there are ways around this, such as using an Alias with a "main" model. But, it's not ideal.
<!-- gh-comment-id:4351261900 -->
@frenzybiscuit commented on GitHub (Apr 30, 2026):
Note that there are ways around this, such as using an Alias with a "main" model. But, it's not ideal.
@frenzybiscuit commented on GitHub (Apr 30, 2026):
I apologize. I will start reading the documents in the future before posting issues. This is a massive piece of software, and I'm still learning about it even today.
<!-- gh-comment-id:4351435392 -->
@frenzybiscuit commented on GitHub (Apr 30, 2026):
I apologize. I will start reading the documents in the future before posting issues. This is a massive piece of software, and I'm still learning about it even today.
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 @frenzybiscuit on GitHub (Apr 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24261
Check Existing Issues
Verify Feature Scope
Problem Description
Currently when the backend model changes (such as if you use OpenAI compatible) the models under workspace/models do not default to the new model. Instead, the model becomes unset and you have to manually set the model. This is very painful to keep updating, especially when you have dozens if not outright hundreds of models.
In addition it confuses the end user as well...
Desired Solution you'd like
When the backend model changes and is no longer available, instead of workspace/models defaulting to unset they instead default to the current active model (the new model).
This could either be completely automated or a global setting/variable in the models section of the admin menu that can be updated manually.
Alternatives Considered
No response
Additional Context
This would solve a lot of grief (for myself, having to update 200+ models. And for my end users, who don't understand what's going on).
@frenzybiscuit commented on GitHub (Apr 30, 2026):
Note that there are ways around this, such as using an Alias with a "main" model. But, it's not ideal.
@Classic298 commented on GitHub (Apr 30, 2026):
https://docs.openwebui.com/reference/env-configuration#enable_custom_model_fallback
@frenzybiscuit commented on GitHub (Apr 30, 2026):
I apologize. I will start reading the documents in the future before posting issues. This is a massive piece of software, and I'm still learning about it even today.