Settings wouldn't allow a save until I changed the Model (that previously worked) - UI issue

[Mustachio77]

App Version

3.11.14

API Provider

OpenRouter

Model Used

claude-3.7-sonnet ; claude-3.7-sonnet:beta

Actual vs. Expected Behavior

Actual Result:
Opening up the settings didn't allow the save button to be pressed; I had to dig around for a while and figure out that the Model value (that was previously working) had to be changed from claude-3.7-sonnet to claude-3.7-sonnet:beta sonnet was no longer an option.

Expected / Ideal Result:

1. If a model version ("model ID" ?) is no longer supported or valid, then make it more obvious to the user that the model has to be changed. Move the error message directly above or below the Model field, the red text warning shouldn't be below the API Provider field
2. Change the message text "model ID" to "Model" in the warning, to exactly match the label "Model", so the label exactly matches the error message.
3. If the model is no longer supported by that API Provider, then remove it completely from the field when the settings are reloaded. In this example, the text field value of anthropic/claude-3.7-sonnet should (ideally) no longer appear at all in the field. Either this should default to another valid choice and make it easy for the user, or clear it completely (so it's more obvious to the user the field is empty and requires a change).

Detailed Steps to Reproduce

1. When initially configuring (for the first time, or for a new API key) select OpenRouter for API Provider
2. Provide a valid API Key
3. Select anthropic/claude-3.7-sonnet (if possible)
4. Wait a while / do some stuff (?) This step is somewhat ambiguous, I didn't notice I couldn't save changes for at least a day
5. Open up settings and attempt to save. Notice if the save button is enabled
6. If disabled, select a value from the Model drop down list. The only value there now is claude-3.7-sonnet:beta
7. Select the only remaining model option, and verify if the message goes away.

Relevant API Request Output

Additional Context

Also found here by another user - https://discord.com/channels/1332146336664915968/1360291117949784165/1360291629491032065

[dosubot]

Hello @Mustachio77! I'm Dosu, a bot here to help you with bugs, answer questions, and assist you in becoming a contributor. I'm here to help while you wait for a human maintainer. How can I assist you today?

The issue you're experiencing seems to be related to the handling of model IDs in the settings UI of Roo Code. When a model becomes unsupported or invalid, the codebase should ideally update the dropdown list to reflect only the valid models. However, it appears that the model "anthropic/claude-3.7-sonnet" was still present, causing confusion and preventing the save action.

Currently, the codebase automatically fetches the list of available models from OpenRouter, and users can refer to the OpenRouter Models page for the complete list ^[1]. If a model is no longer supported, it should be removed from the dropdown list when settings are reloaded, but this functionality might not be working as expected in your case.

Regarding the error message placement and text, it seems like the UI could be improved to make it clearer when a model needs to be changed. The error message should ideally be placed directly above or below the Model field, and the terminology should match the label exactly to avoid confusion.

For a more seamless experience, the codebase should handle the default selection of models when a previously selected model becomes invalid by either defaulting to another valid choice or clearing the field to prompt the user to select a new model. Unfortunately, I couldn't find specific implementation details in the codebase regarding these UI behaviors, which suggests that these features might be missing or under development.

If this issue persists, it might be worth checking for any open issues or submitting a bug report to address these UI concerns.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[Mustachio77]

So I'm back to being able to select any of the 3 original Model options I had (sonnet; sonnet:beta, and sonnet:thinking).
I'm not sure how I got to the point where I could only select the beta version (and it didn't allow sonnet and displayed the error message).

[elianiva]

i'll pull up a PR later for this one if no one fixed it yet, it should be as simple as filtering invalid models and making the error message clearer

[daniel-lxs]

Hey @elianiva, do you still want to take this one?