Closed ryansereno closed 9 months ago
Now that I'm thinking through this more, changing the default model env param would probably resolve this... But I know you'd like to move toward the ability to add/ delete models, so there might still be a need to default to whatever model is available?
Super! This makes a lot of sense! Thanks @ryansereno
@ivanfioravanti Wanted to let you know that this has broken the application for me; after conversations have been cleared/ default model is not installed, it's no longer allowing me to create any new conversations. Trying to find a solution, but feel free to revert in the meantime.
Simpler fix might just be to alert of the default model is not installed, looking into this now.
Sorry for the many updates today. I went ahead and put in that PR for alerting if the default/ fallback model isn't installed.
As long as the user goes ahead and installs the default model or changes their fallback model to something that is installed, this PR is still relevant.
Once I set my fallback model to be the one I have installed, this useEffect to update the selected model works fine.
The model selector cannot handle the case where no llama:latest model is available, and only a single ollama model was available, when creating a new conversation. Tries to default to llama:latest, but it does not exist, and dropdown selector does not allow selection of existing model. Added useEffect to use whatever model is available.