No model available. Check policy enablement under GitHub Settings > Copilot

[sbroenne]

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

1. Open Copilot
2. Try any prompt - triggers the error
3. /model - no models availlable Some models are not available due to configured policy.

Expected behavior

Model are available.

Additional context

No response

[irodneyedwards]

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).

[christophepuga-netatmo]

When downgrading to 0.0.330, the /model is working again. Seems to be a regression.

[mcanouil]

It appears, authenticating via GitHub CLI does not lead to the issue with 0.0.351.

[angelser]

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.

[mcanouil]

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.

[tuminoid]

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.

[andyfeller]

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. 🤔

[tuminoid]

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.

[rahfar]

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)

[jonathanjeurissen-quantum]

Same problem here with version 0.0.353. The revert to 0.0.330 worked indeed. Using GitHub Copilot Business.

[SebRosander]

We're seeing a similar issue here:

0.0.353 not working:

0.0.330 working:

[farcel]

+1

[jbollman7]

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