Github Copilot for Business, failing to configure and use
Describe the bug We are in corporate environment, using Copilot for Business subscriptions, not many features/models are enabled. Copilot in VScode IDE works fine, I am unable to use it with Goose CLI or the Desktop app
To Reproduce Try to configure goose: goose configure --> I am able to perform github device auth flow. --> model listing fails.
Try to use goose: goose, fails (see screenshots)
Expected behavior I should be able to chat with gpt-4o, this model is enabled for the organisation.
Screenshots
Please provide the following information
- OS & Arch: MacOS
- Interface: UI / CLI
- Version: v1.14.0
- Extensions enabled: Computer Controller, Developer
- Provider & Model: gpt-4o
I have a github Copilot Pro plan and the registration doesn't work for me either
using version 1.14.2
`$ goose configure
This will update your existing config files if you prefer, you can edit them directly at /home/davide/.config/goose
┌ goose-configure
│
◇ What would you like to configure?
│ Configure Providers
│
◇ Which model provider should we use?
│ GitHub Copilot
│
● GITHUB_COPILOT_TOKEN is already configured
│
◇ Would you like to update this value?
│ Yes
│
● Configuring GITHUB_COPILOT_TOKEN using OAuth device code flow...
│
■ Failed to authenticate: Execution error: OAuth configuration not supported by this provider
│
Error: OAuth authentication failed for GITHUB_COPILOT_TOKEN: Execution error: OAuth configuration not supported by this provider
`
errors from the UI client too
there's something really off somewhere. I've just run these steps:
- from UI, configured a Tetrate account
- from UI, deleted github copilot current configuration
- from UI, noticed that I can't select any model from tetrate, list is empty and pasting a model results in no model
- from terminal I start "goose configure" and selected "Tetrate Agent Router Service" to try reconfigure it
- the cli guides me to ...connect to github copilot
Today's update with a new proxy setting, i am able to move 1 bit forward, but not there yet!
` (.venv) >goose configure
This will update your existing config files if you prefer, you can edit them directly at /Users/redacted/.config/goose
┌ goose-configure
│
◇ What would you like to configure?
│ Configure Providers
│
◇ Which model provider should we use?
│ GitHub Copilot
│
● GITHUB_COPILOT_TOKEN is already configured
│
◇ Would you like to update this value?
│ Yes
│
● Configuring GITHUB_COPILOT_TOKEN using OAuth device code flow...
│
◆ OAuth authentication completed successfully!
│
◇ Model fetch complete
│
└ Request failed: error decoding response body
`
@harkamals @SirStone would you be able to share your config.yaml at all? (not sure if these things are related, don't know anything about copilot model serving
@blackgirlbytes do you you have access to copilot models to try this? And I think the oauth stuff (in GUI) is broken (or incomplete I should say which is slightly confusing - looking at that separately).
@harkamals not sure how to chase this down, as I connected it to what I have of copilot enterprise (not sure if that is the same as business) and it did list models, (I picked gpt-5 - I am lucky enough to see it in the list!). did the cli show you the link and do oauth correctly? (I am guessing by the screenshot - yes?).
One possibility is that it is hanging on to an old token - @harkamals did you have it working with goose previously? or never has worked (there may be limitations if the latter for some subscriptions).