Skip to content

Goose + Github Copilot in WSL: OAuth authentication failed for GITHUB_COPILOT_TOKEN #6607

@ragasits

Description

@ragasits

I'm trying to configure my new Enterprise-level Github Copilot access, but unfortunately I keep getting an OAuth error.

My environment:

  • Windows 11 Enterprise + WSL (Ubuntu)
  • Goose install: goose-x86_64-unknown-linux-gnu.tar.bz2
  • Goose version: 1.20.1

Configure Github copilot

rgt@DEST-CL-225:/mnt/c/0.job/dev$ goose configure

This will update your existing config files
if you prefer, you can edit them directly at /home/rgt/.config/goose

┌ goose-configure

◇ What would you like to configure?
│ Configure Providers

◇ Which model provider should we use?
│ GitHub Copilot

● Configuring GITHUB_COPILOT_TOKEN using OAuth device code flow...

Please visit https://github.com/login/device and enter code AAAA-BBBB
■ Failed to authenticate: Execution error: Failed to save token: Failed to access keyring: Platform secure storage failure: DBus error: The name org.freedesktop.secrets was not provided by any .service files

Error: OAuth authentication failed for GITHUB_COPILOT_TOKEN: Execution error: Failed to save token: Failed to access keyring: Platform secure storage failure: DBus error: The name org.freedesktop.secrets was not provided by any .service files
rgt@DEST-CL-225:/mnt/c/0.job/dev$

In Browser:

I successfully added the generated code in the browser before receiving the "OAuth authentication" error:

Congratulations, you're all set!
Your device is now connected.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions