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

Invalid models shown when switching providers #787

Closed
angiejones opened this issue Jan 26, 2025 · 1 comment · Fixed by #789
Closed

Invalid models shown when switching providers #787

angiejones opened this issue Jan 26, 2025 · 1 comment · Fixed by #789
Labels
bug Something isn't working

Comments

@angiejones
Copy link
Collaborator

I was using OpenAI then wanted to switch to Gemini. When prompted for the model from my new provider, configure gives the model from the current provider. Seems it's pulling this from `/.config/goose/config.yaml as opposed to pulling the appropriate models for the selected provider.

┌   goose-configure 
│
◇  What would you like to configure?
│  Configure Providers 
│
◇  Which model provider should we use?
│  Google Gemini 
│
●  GOOGLE_API_KEY is already configured
│  
◇  Would you like to update this value?
│  No 
│
◆  Enter a model from that provider:
│  gpt-4o (default)
└  

Here's an example when going from Gemini to Ollama

┌   goose-configure
│
◇ What would you like to configure?
│ Configure Providers
│
◇ Which model provider should we use?
│ Ollama
│
◇ Enter a model from that provider:
│ gemini-2.0-flash-exp
│
◐ Checking your configuration...                                                   ExecutionError("error sending request for url (http://localhost:11434/v1/chat/completions)")
◇ We could not connect!
│
└ The provider configuration was invalid
@angiejones angiejones added the bug Something isn't working label Jan 26, 2025
@angiejones
Copy link
Collaborator Author

Note, that I am able to type the correct model but I would have to know its name. A bit difficult when it's something like gemini-2.0-flash-exp

baxen added a commit that referenced this issue Jan 26, 2025
Only an active env var can override this, which is still useful
for installers

Fixes #787
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant