Bug Report: Custom Provider Models Not Showing in Combo Model Selector
Summary
Models added to a custom OpenAI-compatible provider are not displayed in the Combo editor's model selector. Only a placeholder model-id appears instead of the actual configured models.
Environment
- 9router Version: v0.5.8
- OS: Windows Server 2022
- Browser: Chrome
Steps to Reproduce
- Create a custom OpenAI-compatible provider named "华为云" (Huawei Cloud)
- Add an API key connection with name
hw
- Add models to the provider (e.g.,
glm-5.2, glm-5.1, deepseek-v4-flash)
- Navigate to Combos page → Click Edit on any combo → Click Add Model
- In the model selector popup, search for
hw or look under "华为云" section
Expected Behavior
The model selector should display all models added to the Huawei Cloud provider:
hw/glm-5.2, hw/glm-5.1, hw/deepseek-v4-flash, etc.
Actual Behavior
The model selector only shows one placeholder entry: hw/model-id
The actual configured models do not appear.
Comparison with Working Provider
| Provider |
Connection Name |
Model Prefix |
Shows in Selector |
| 华为云 |
hw |
hw/ |
❌ No (only hw/model-id) |
Root Cause
Frontend state synchronization issue - the model selector component reads from a different data source than the provider detail page.
Impact
Users cannot add custom provider models to new combos via the UI.
Bug Report: Custom Provider Models Not Showing in Combo Model Selector
Summary
Models added to a custom OpenAI-compatible provider are not displayed in the Combo editor's model selector. Only a placeholder
model-idappears instead of the actual configured models.Environment
Steps to Reproduce
hwglm-5.2,glm-5.1,deepseek-v4-flash)hwor look under "华为云" sectionExpected Behavior
The model selector should display all models added to the Huawei Cloud provider:
hw/glm-5.2,hw/glm-5.1,hw/deepseek-v4-flash, etc.Actual Behavior
The model selector only shows one placeholder entry:
hw/model-idThe actual configured models do not appear.
Comparison with Working Provider
hw/model-id)Root Cause
Frontend state synchronization issue - the model selector component reads from a different data source than the provider detail page.
Impact
Users cannot add custom provider models to new combos via the UI.