GitHub Copilot Config issue

[daytrdr]

Describe the bug
When configuring the GitHub Copilot provider via the CLI or UI, the configure_provider_dialog() function prompts the user to manually enter a GITHUB_COPILOT_TOKEN via password input. However, this bypasses the OAuth device code authentication flow implemented in GithubCopilotProvider. As a result, the expected login process is never triggered during configuration.

To Reproduce
Steps to reproduce the behavior:

Run the Goose CLI or UI
Select GitHub Copilot as the provider in the configuration dialog
Observe that it prompts for a GITHUB_COPILOT_TOKEN manually
Notice that the OAuth device code flow does not initiate
Expected behavior
Instead of prompting for manual token entry, the configuration flow for GitHub Copilot should detect that the provider supports OAuth and trigger the device code login flow automatically. This behavior is already implemented and works when the provider is used during a completion request.

Screenshots
N/A

Please provide following information:

OS & Arch: macOS Sequoia 15.5 / Apple Silicon (ARM)
Interface: CLI and UI
Version: v1.0.30
Extensions enabled: [Please specify, e.g. Computer Controller, Figma, etc.]
Provider & Model: GitHub Copilot
Additional context
The OAuth flow only triggers under specific conditions:

The provider is used for a completion request
refresh_api_info() is called
No token exists in config storage
Only then does get_access_token() eventually call login() to initiate the device code flow. This logic should ideally be triggered during provider configuration for those that support it.

[atarantino]

I've been following the same problem with this issue as well.

I made a comment over there, but I have a PR open to fix the cli portion of this issue. Take it with a grain of salt though, I have very little Rust experience . Just looking to help and learn 😄

[daytrdr]

Thanks for commenting... let me see if I can also test your PR. CLI only is an easy work around for now.

[whitehat101]

The latest version that I can use with GitHub Copilot is v1.0.28. I am able to connect via the cli and then send messages using the app.

If I connect with the cli on v1.0.28, I can use the GUI app with Copilot through v1.0.31 after that It forces me to pick a model.

[joemccall86]

FWIW this problem never happened for me, but now that copilot has been commented out I can no longer use it with the latest goose. Can we add it back in and mark it as "(experimental)"?

[dogederp]

FWIW this problem never happened for me, but now that copilot has been commented out I can no longer use it with the latest goose. Can we add it back in and mark it as "(experimental)"?

I agree. I would like to still have this as an option before the actual issue gets fixed.

[atarantino]

@EbonyLouis since #3157 was merged to fix the CLI Copilot integration, can we re-enable since it was removed in #3199? Or do we need to fix the desktop integration first?

[chuan29812]

@EbonyLouis since #3157 was merged to fix the CLI Copilot integration, can we re-enable since it was removed in #3199? Or do we need to fix the desktop integration first?

LOL, why was it not a commenting-out in the Desktop UI especially after the cli portion was fixed. Since the original issue that targets the desktop portion has been sitting idle for a month and half. I guess the only immediately solution is to use a fork or downgrade

[atarantino]

@chuan29812 they are aware. There is an open PR to re-enable it. #3931