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

failing to run Goose on my system #61

Open
PaulConyngham opened this issue Sep 11, 2024 · 2 comments
Open

failing to run Goose on my system #61

PaulConyngham opened this issue Sep 11, 2024 · 2 comments

Comments

@PaulConyngham
Copy link

PaulConyngham commented Sep 11, 2024

Goose is failing to run on my system.

In the terminal I am initialising the key as an environment variable like so:

export OPENAI_API_KEY=xxxxxx

I am getting the following error every time I run the project:

Screen Shot 2024-09-12 at 8 33 39 am

The key is active and is being called. As you can see an update on OpenAi's side (The last time I tried using this key was for Goose today , the 12th of Sept 2024):

Screen Shot 2024-09-12 at 8 42 41 am

Noticed we are using pipx so my python version should not be affecting this. But to test outside of this ran it in a python 3.12 conda env too and via the vanilla terminal

It would be great to see what is actually going on under the hood here with a verbose output flag for Goose, perhaps something like: goose session start -v

@baxen
Copy link
Collaborator

baxen commented Sep 12, 2024

I think most likely this is because the API key does not have access to the model. We have some updates in progress to catch that and similar cases more clearly! Verbose mode is also a good idea here.

To try to confirm this, if you have an openai with chatgpt enabled, you likely separately have to enable billing for the API at platform.openai.com. Do you see API credits remaining at https://platform.openai.com/settings/organization/billing/overview?

@baxen
Copy link
Collaborator

baxen commented Sep 15, 2024

Did you have any luck with this? if you upgrade, square/exchange#48 should show a much more clear error message

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

No branches or pull requests

2 participants