github
No model available. Check policy enablement under GitHub Settings > Copilot
Describe the bug
I use Copilot through my organization. Copilot works on Github, VSCode, etc. but stopped working on the CLI a few weeks ago. It used to work!
Error: ✗ No model available. Check policy enablement under GitHub Settings > Copilot
CLI Settings are enabled.
I am a Microsoft employee and use my linked Github account if that helps troubleshooting.
Affected version
0.0.351 Commit: 90770bc
Steps to reproduce the behavior
- Open Copilot
- Try any prompt - triggers the error
- /model - no models availlable Some models are not available due to configured policy.
Expected behavior
Model are available.
Additional context
No response
I have this exact issue. I’m using version 0.0.351 (commit 90770bc) and I’m getting ‘✗ No model available…’ despite being logged in and having access elsewhere. I’m also a Microsoft employee (if that helps).
When downgrading to 0.0.330, the /model is working again. Seems to be a regression.
It appears, authenticating via GitHub CLI does not lead to the issue with 0.0.351.
It appears, authenticating via GitHub CLI does not lead to the issue with 0.0.351.
What are your steps? I just tried authenticating with Github CLI and then running copilot cli but did not seem to make a difference.
Unfortunately, for now I can't replicate, but my colleagues logged in via GitHub CLI can see the models while all my colleagues (including me) logged in directly via Copilot CLI can't access the models.
I'm all of a sudden getting this issue. Version 0.0.352, and no matter if authed via GH CLI or Copilot CLI, I get no models available. I'm admin of the organization providing the Copilot access for our team, and I definitely have models available.
Downgrading Copilot CLI to 0.0.351 or 0.0.350 does not help.
edit: Downgrading to 0.0.330 as mentioned before does help though. Anything newer than that fails.
First, I appreciate everyone rallying together to help figure this out. 🙇
I'd be curious if others could confirm if they're seeing the same errors listed in #346, which I suspect might be the same problem. 🤔
I'd be curious if others could confirm if they're seeing the same errors listed in #346, which I suspect might be the same problem. 🤔
I have same as this comment. To add, the problem started today when I updated to 0.0.352 and/or something forced a re-login on me. I'm fairly confident the previous token copilot was using from gh auth was from some time ago, when I still had personal Copilot license. We only recently moved to business license. This would stem with the suspected endpoint issue described in #346 . Especially when I had successfully used 0.0.350 and 0.0.351 and other versions newer than 0.0.330 with the old auth.
edit: on another machine I have copilot 0.0.351 installed and old gh auth token, and models are working fine. edit2: using PAT as described here solves the issue for me, I can use 0.0.352 or 0.0.353 with PAT token.
I have the same issue. On my working account all mentioned above is reproduced. With PAT latest version is working With auth from gh, working only if downgrade to 0.0.330 (with 0.0.331 error appears)
Same problem here with version 0.0.353. The revert to 0.0.330 worked indeed. Using GitHub Copilot Business.
We're seeing a similar issue here:
0.0.353 not working:
0.0.330 working:
We're seeing a similar issue here:
0.0.353 not working:
0.0.330 working:
Exact same situation, working with 0.0.330 is the working version. Thanks everyone
I ran into the same issue and was able to resolve it by going to the Copilot settings under the organization. There was a feature flag that had the CLI disabled. After enabling it, all selected/enabled models started to show up and I was able to use the CLI without problems.
Hope that helps!
I ran into the same issue and was able to resolve it by going to the Copilot settings under the organization. There was a feature flag that had the CLI disabled. After enabling it, all selected/enabled models started to show up and I was able to use the CLI without problems.
Hope that helps!
Similar but I had to go into our parent Enterprise -> AI Controls, and the option for Copilot CLI wasn't set at all. Once I changed it to Let organizations decide, I was able to go into the specific Org and enable it and then Copilot CLI started working
Problem solved for me also, not sure that we changed anything in org settings, but now it works with current and previous versions
Upgraded from 0.0.330 to version 0.0.354 here but it immediately broke again.
~~Same here, using Copilot Business, can use it perfectly fine in Zed, gives "no model available" in cli.~~ - it was indeed disabled in policies, my bad.
Upgraded from 0.0.347 to 0.0.354 and got the same issue here.
Roll back to old versions will give:
✗ No model available. Check policy enablement under GitHub Settings > Copilot
/model works fine (not working at 0.0.354).
posting this in case it helps someone else.
at my job, we use github cloud enterprise, we had 2 orgs setup for the different levels(business vs enterprise).
i happened to be in both. for whatever reasons that meant that i would not get any premium models.
we figured this out because intellij and vscode recently also stopped working, meaning that i lost all my premium models in both of those IDEs as well as copilot cli.
once i was removed from the business org, my premium models started showing up again.
Although yesterday, version 0.0.355 worked fine, today it's broken again. @sbroenne Is it still working for you?
Anything above v0.0.330 might work for a short while, then return to empty model. One can fiddle about with gh auth login vs copilot login, see the models flash on the screen when executing /models and then it returns to an empty list again.
EDIT: Got stuck at the same point as the comment below, "You are not authorized...".
After downgrading to 0.0.330, I'm being locked out of doing any requests with error message "You are not authorized to use this Copilot feature, it requires an enterprise or organization policy to be enabled." This also happened last week to me after downgrading (and got auto-resolved after about 4 days).
Any way around that? Tried logging out and in through Copilot and tried gh auth login as well, but no luck either.
We have a fix that addresses the majority of issues in this thread. It will be released in the next 48 hours, but we will leave this issue open for a day or so afterwards to ensure we get feedback from those impacted.
I'm not sure if this is directly related, but in case someone encounters the same issue, I still leave it here.
All of these happened to me:
- I updated copilot, and it was broken.
- I rolled back to an old version and re-logged-in, and it worked.
- I did nothing, and it was broken, again.
- I updated to a new version, and it was still broken.
- I did nothing, and it worked.
Whenever it was broken like showing ✗ No model available., my GitHub Settings > Copilot couldn't display my org name.
The fix we shipped landed in 0.0.560. Could folks on this thread check and see if this issue is resolved?
Updated to v0.0.361-0 and it shows model list briefly (like for 1-2 seconds) with /model and then the list disappears, saying "✘ Execution failed: No model available. Check policy enablement under GitHub Settings > Copilot"
If I quickly press model option, ex 4, i am able to select model, but then it fails with following messages.
copilot
Welcome to GitHub Copilot CLI
Version 0.0.361-0 · Commit 5659eac
Copilot can write, test and debug code right from your terminal. Describe a task to get started or enter ? for help. Copilot uses AI, check for mistakes.
● **Model changed to: gpt-5**. The new model will be used for the next conversation.
● Connected to GitHub MCP Server
● Logged in as user: redacted
> hello world in python
✘ Execution failed: No model available. Check policy enablement under GitHub Settings > Copilot
Select Model
Choose the AI model to use for Copilot CLI. The selected model will be persisted and used for future sessions.
Some models are not available due to configured policy.
❯ 1. Cancel (Esc)
Confirm with number keys or ↑↓ keys and Enter, Cancel with Esc
