-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choosing a model should be exclusively done through the UI. #1894
Comments
I'm not quite sure I understand what you mean. The current frontend already allows for selecting the model and API key. What additional support would you like to see added? |
For instance, the documentation regarding groq integration requires API Key to be provided at the time of starting the container: I am suggesting no LLM related information should ever be required at the time of starting the container. All LLM related settings should be done through the existing UI form. |
Perhaps we can support inputting the Groq API key when using the Groq model and the Gemini API key when using the Gemini model, and so on... |
I would suggest to have a smarter form. We can make the API key a mandatory field if you choose an online LLM provider like groq or gemini. If local (Ollama) is being used, then the API Key field won't appear or at least becomes non-mandatory. |
I think we could fix that documentation to clarify that
Please do tell if I'm missing something. @alimsyed just to note:
|
@alimsyed I just checked for that document, and it doesn't exist in OpenDevin, it's only a branch. It's because the PR proposing the Groq document has not been merged: And I don't find that page on the documentation site: I think that's okay, precisely because there does not seem to be something particular about Groq on this issue, it works like other providers, already like you propose: from the UI. I will close this issue, please do let us know though if there are any problems. |
What problem or use case are you trying to solve?
The settings for choosing the LLM you want to use is not clear. This way, if you want to switch up the LLM behind the scene (which you do want to do often) you don't have to restart the setup. The frontend form would allow you to choose the LLM the way it does now.
Describe the UX of the solution you'd like
By allowing choosing of LLM exclusively through the frontend will remove a lot of ambiguity and make life much easier for the average user, driving up interest.
Do you have thoughts on the technical implementation?
The implementation for this shouldn't be difficult. The form responsible for settings up LLM should also allow saving API keys if user chooses to so so.
Describe alternatives you've considered
Additional context
Making the project more user friendly is going to drive up usage.
The text was updated successfully, but these errors were encountered: