Disabled Models Still Appear While Enabled Models Disappear in Model Selection #3031

New Issue

2025-11-11T15:20:04-06:00

GiteaMirror commented

2025-11-11 15:20:04 -06:00

Originally created by @honwei189 on GitHub (Dec 17, 2024).

Description:
When I disable specific 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 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.1 70B Instruct (Model ID: meta-llama/llama-3.1-70b-instruct)
- Meta: Llama 3.1 70B Instruct (free) (Model ID: meta-llama/llama-3.1-70b-instruct:free)
If I disable Meta: Llama 3.1 70B Instruct, and then open a new chat, the model list incorrectly displays Meta: Llama 3.1 70B Instruct (the disabled model) while omitting Meta: Llama 3.1 70B Instruct (free) (the enabled model).

Steps to Reproduce:

Go to Admin -> Settings > Model.
Disable a model with a suffix-free name, such as Meta: Llama 3.1 70B Instruct.
Leave enabled its variant, e.g., Meta: Llama 3.1 70B Instruct (free).
Open a new chat and attempt to select a model.

Expected Behavior:

The disabled model (Meta: Llama 3.1 70B Instruct) should not appear in the model selection list.
The enabled model (Meta: Llama 3.1 70B Instruct (free)) should appear in the model selection list.

Actual Behavior:

The disabled model (Meta: Llama 3.1 70B Instruct) incorrectly appears in the list.
The enabled model (Meta: Llama 3.1 70B Instruct (free)) does not appear.

Additional Context:
Please see the attached screenshot for a visual example of the issue.

This bug causes confusion when selecting models, particularly when managing large lists with similarly named entries. Resolving this issue will significantly improve model management usability.

Attachment(s):

Originally created by @honwei189 on GitHub (Dec 17, 2024). **Description:** When I disable specific 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 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.1 70B Instruct` (Model ID: `meta-llama/llama-3.1-70b-instruct`) - `Meta: Llama 3.1 70B Instruct (free)` (Model ID: `meta-llama/llama-3.1-70b-instruct:free`) - If I disable `Meta: Llama 3.1 70B Instruct`, and then open a new chat, the model list **incorrectly displays** `Meta: Llama 3.1 70B Instruct` (the disabled model) while **omitting** `Meta: Llama 3.1 70B Instruct (free)` (the enabled model). --- **Steps to Reproduce:** 1. Go to **Admin -> Settings > Model**. 2. Disable a model with a suffix-free name, such as `Meta: Llama 3.1 70B Instruct`. 3. Leave enabled its variant, e.g., `Meta: Llama 3.1 70B Instruct (free)`. 4. Open a new chat and attempt to select a model. **Expected Behavior:** - The disabled model (`Meta: Llama 3.1 70B Instruct`) should not appear in the model selection list. - The enabled model (`Meta: Llama 3.1 70B Instruct (free)`) should appear in the model selection list. **Actual Behavior:** - The disabled model (`Meta: Llama 3.1 70B Instruct`) incorrectly appears in the list. - The enabled model (`Meta: Llama 3.1 70B Instruct (free)`) does not appear. --- **Additional Context:** Please see the attached screenshot for a visual example of the issue. This bug causes confusion when selecting models, particularly when managing large lists with similarly named entries. Resolving this issue will significantly improve model management usability. --- **Attachment(s):** ![2024-12-17_085717](https://github.com/user-attachments/assets/ba1f752a-7e36-4788-ae1d-a044feb24cfe) ![2024-12-17_085810](https://github.com/user-attachments/assets/395e5d5f-86f3-421c-abcd-19e719bf68f5)

GiteaMirror closed this issue

2025-11-11 15:20:04 -06:00

GiteaMirror referenced this issue

2026-04-20 02:37:43 -05:00

[GH-ISSUE #23695] issue: Voice recording interrupted by screen lock on iPhone PWA (Wake Lock API missing in VoiceRecording component) #20047

GiteaMirror referenced this issue

2026-04-25 09:45:48 -05:00

[GH-ISSUE #23695] issue: Voice recording interrupted by screen lock on iPhone PWA (Wake Lock API missing in VoiceRecording component) #35576

GiteaMirror referenced this issue

2026-05-05 23:45:01 -05:00

[GH-ISSUE #23695] issue: Voice recording interrupted by screen lock on iPhone PWA (Wake Lock API missing in VoiceRecording component) #58713

GiteaMirror referenced this issue