You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Remove all old Goose configs
Install goose on MacOS
Add working OpenAI API key in settings
This error gets triggered and shows the wrong API key (based on the final characters).
Ran into this error: Authentication error: Authentication failed. Please ensure your API keys are valid and have the required permissions. Status: 401 Unauthorized. Response: Object {"error": Object {"code": String("invalid_api_key"), "message": String("Incorrect API key provided: sk-proj-********************************************************************************************************************************************************TGUA. You can find your API key at https://platform.openai.com/account/api-keys."), "param": Null, "type": String("invalid_request_error")}}.
Please retry if you think this is a transient or recoverable error.
====
Expected behavior
I thought that putting in a new API key would store it and overwrite the old one. I thought that clearing configurations would fix this issue by removing prior configs. I used these techniques before installation:
You can remove all of this data by following these steps.
stop any copies of goose running (CLI or GUI)
consider confirming you've stopped them all via the activity monitor
open the keychain and delete the credential called "goose", which contains all secrets stored by goose
rm -rf ~/.config/goose
If you are using Goose Desktop on macOS, you may also need to remove the app itself.
rm -rf ~/Library/Application Support/Goose
Delete the "Goose" app from your Applications folder
After this cleanup, if you are looking to try out a fresh install of Goose, you can now start from the usual install instructions.
Screenshots
If applicable, add screenshots to help explain your problem.
Please provide following information:
OS & Arch: MacOS Sequoia 15.4.1 ARM64
Interface: UI
Version: v1.0.18-22
Extensions enabled: Computer Controller, Developer, Knowledge Graph Memory, Memory, Git, PDF Reader -- It has been tested with all deactivated and it has the same issue.
Provider & Model: openAI gpt-4o
Additional context
the API key is can run in CODEX in CLI on the same machine.
The text was updated successfully, but these errors were encountered:
I put the API key for OpenAI as a line in my shell rc file and when I edited it for something else (nano ~/.zshrc) I saw that I had permanently added the dead API key to my system. When I removed this export API key line from the file, goose CLI and goose GUI both worked fine. I am not a smart man.
Describe the bug
Note: Please check the common issues on https://block.github.io/goose/docs/troubleshooting before filing a report
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Ran into this error: Authentication error: Authentication failed. Please ensure your API keys are valid and have the required permissions. Status: 401 Unauthorized. Response: Object {"error": Object {"code": String("invalid_api_key"), "message": String("Incorrect API key provided: sk-proj-********************************************************************************************************************************************************TGUA. You can find your API key at https://platform.openai.com/account/api-keys."), "param": Null, "type": String("invalid_request_error")}}.
Please retry if you think this is a transient or recoverable error.
====
Expected behavior
I thought that putting in a new API key would store it and overwrite the old one. I thought that clearing configurations would fix this issue by removing prior configs. I used these techniques before installation:
You can remove all of this data by following these steps.
stop any copies of goose running (CLI or GUI)
consider confirming you've stopped them all via the activity monitor
open the keychain and delete the credential called "goose", which contains all secrets stored by goose
rm -rf ~/.config/goose
If you are using Goose Desktop on macOS, you may also need to remove the app itself.
rm -rf ~/Library/Application Support/Goose
Delete the "Goose" app from your Applications folder
After this cleanup, if you are looking to try out a fresh install of Goose, you can now start from the usual install instructions.
Screenshots
If applicable, add screenshots to help explain your problem.
Please provide following information:
Additional context
the API key is can run in CODEX in CLI on the same machine.
The text was updated successfully, but these errors were encountered: