mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #8076] Bug: Disabled Models (same model name but different id) Still Appear While Enabled Models Disappear in Model Selection #53654
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#53654
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 @honwei189 on GitHub (Dec 26, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8076
The problem still exists and has never been solved in 0.5.0.
The bug is of critical nature. The utilization of an incorrect model has led to me incurring a different cost.
When I disable some OpenRouter models (e.g., those with the same name but with a suffix like "(free)" or ":free") under Admin -> Settings > Model, I encounter an issue where the disabled models still appear in the chat screen model selection list when starting a new chat, while the enabled models disappear. (file attached below)
For example:
The model list contains two similar entries:
Meta: Llama 3 8B Instruct (Model ID: meta-llama/llama-3-8b-instruct)
Meta: Llama 3 8B Instruct (free) (Model ID: meta-llama/llama-3-8b-instruct:free)
If I disable Meta: Llama 3 8B Instruct, and then open a new chat, the model list incorrectly displays Meta: Llama 3 8B Instruct (the disabled model) while omitting Meta: Llama 3 8B Instruct (free) (the enabled model).
I checked OpenRouter API history log. It's using a disabled model id.
Model selection list in chat screen:
Models list in Admin -> Setting -> Models
