Goose CLI crashes when it can't write to the keyring without reporting what went wrong

[SigmaEnterprise]

No matter what I try on WSL on windows ,it keeps exiting when I try to load model at final step it keeps exiting and never saves config settings

WSL Ubuntu 22.04

Any help would be appreciated

It always just exits at that final step

[bjornbyte]

I believe I'm hitting the same bug (Windows 11 WSL2) trying to configure goose with copilot:

❯ goose configure

Welcome to goose! Let's get you set up with a provider.
  you can rerun this command later to update your configuration

┌   goose-configure
│
◇  Which model provider should we use?
│  Github Copilot
│
◇  Enter a model from that provider:
│  gpt-4o
│
◇  Execution error: failed to get api info after 3 attempts
│
└  Failed to configure provider: init chat completion request with tool did not succeed.

  Warning: We did not save your config, inspect your credentials
   and run 'goose configure' again to ensure goose can connect

I tried to check the logs but the path reported by goose info for logs (and other things), ~/.local/state/goose/logs does not exist.

[bjornbyte]

although I just tried configuring with google gemini and succeeded, so maybe a different but similar problem. Let me know if I should open a separate ticket.

[GitMurf]

You need to disable the secure storage stuff by setting this env variable: export GOOSE_DISABLE_KEYRING=true

I got copilot to work after I did this.

I did try gemini as well and got that to work first so if for whatever reason copilot doesn't work right away, try getting google gemini to work first and then try copilot again.

[bjornbyte]

that worked, thanks!

[SigmaEnterprise]

I'm using it with no problems on MX Linux Libretto 23.6

[DOsinga]

yeah, export GOOSE_DISABLE_KEYRING=1 seems to do the trick. however we should default to that if writing to the keyring fails. it seems hard to keep this sort of thing working on all linux varieties