Skip to content
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

Goose UI can have issues if there are lingering configs in Local storage #1003

Open
Kvadratni opened this issue Jan 31, 2025 · 4 comments
Open
Assignees
Labels

Comments

@Kvadratni
Copy link
Collaborator

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.

@alexhancock
Copy link
Collaborator

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

@Kvadratni
Copy link
Collaborator Author

essentially I had 400's from openAI models until I entirely deleted local storage and restarted with a fresh config

@pascalwengerter
Copy link

pascalwengerter commented Feb 1, 2025

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

@hamlim
Copy link

hamlim commented Feb 20, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants