Goose UI can have issues if there are lingering configs in Local storage
I had an issue running OpenAI models due to leftover data in my local storage. After manually resetting it , everything works.
We should add a "reset config) option to setting to allow for better UX when configuration changes.
Can you describe the issue in more detail?
I'm looking into a large refactor of config/local storage soon, so want to make sure I address failure modes
essentially I had 400's from openAI models until I entirely deleted local storage and restarted with a fresh config
Can confirm this. When switching to my Ollama provider the localStorage (accessible via ⌥ + ⌘ + I on MacOS) gets set to qwen2.5 and I need to manually set it to the actual model I'm running for it to work
I ran into a similar issue when swapping the model I was serving locally (using LM Studio to launch the server) - I swapped between two models while keeping the Goose UI running.
Clearing all application storage and then quitting and re-launching it seemed to get it working again for me.
Should be fixed in the updated UI!