Unable to use Github Copilot device authentication flow

[drj613]

Describe the bug
Selecting Github Copilot in both the UI and CLI versions of Goose is prompting for an API key rather than using Copilot's device auth.

To Reproduce
Steps to reproduce the behavior:

1. Install Goose
2. When configuring providers, click Github Copilot
3. Prompt appears for Github Copilot token

Expected behavior
I expected a prompt to visit https://github.com/login/device and enter a code.

Screenshots

Please provide following information:

• OS & Arch: MacOS Sonoma 14.2.1
• Interface: Both
• Version: UI 1.0.29; CLI 1.0.29
• Extensions enabled: n/a
• Provider & Model: Github Copilot

Additional context
Tried installing CLI with curl and brew
Tried installing UI via brew and zipped executable

[drj613]

Apologies if there's some way to get this token that I've missed - all other tools I've tried have given a prompt along the lines of this one:

┌  Add credential
│
◇  Select provider
│  GitHub Copilot
│
◇   ──────────────────────────────────────────────╮
│                                                 │
│  Please visit: https://github.com/login/device  │
│  Enter code: XXXX-XXXX                      │
│                                                 │
├─────────────────────────────────────────────────╯
│
◇  Login successful
│
└  Done

[Jaboo9]

@drj613 I think you can use a personal access token

[drj613]

@drj613 I think you can use a personal access token

This worked to at least get me past the onboarding flow but I'm getting failure messages with every attempt at a message

[Jaboo9]

Could you try the CLI?

[drj613]

@Jaboo9 no luck

[silentius-satoshi]

I followed the same exact steps mentioned above (GUI version) and it reproduced a similar behavior outcome:
"Ran into this error: Execution error: failed to get api info after 3 attempts.
Please retry if you think this is a transient or recoverable error."

@Jaboo9 Can you provide step-by-step instructions in properly acquiring the "GITHUB_COPILOT_TOKEN" that it's asking for so that we can see if there's a difference between our steps? For instance, start from the beginning choosing between "Classic" and/or "Fine-Grained Token" Personal Access Tokens.

[Juliuzzk]

Same problem here, i cant find what token i need to provide

[Crescent617]

Same case here... also cannot find token

[infinitybiscuit]

Also getting the same problem. Tried generating a Personal Access Token(Classic) with permission to CoPilot but I get...

◇ Execution error: failed to get api info after 3 attempts
│
└ Failed to configure provider: init chat completion request with tool did not succeed.

[renzo4web]

Same problem here!

[atarantino]

I ran into this as well and figured I'd take a stab at fixing it.

I have a PR here if you're interested in the changes. The fork linked is here. For now, you'd have to clone my fork and build it locally in order to get copilot working. There are instructions in CONTRIBUTING.MD that state how to compile and run goose locally.

I only implemented the fix through the cli, not the web app yet. But once you configure it through the cli, the web app will work as well if you prefer that.

Hopefully I can get some feedback on my PR soon.

[AsalcedoTellusant]

I'm also experiencing this issue when trying to configure GitHub Copilot as a provider via goose configure.