github / github/copilot-cli

Copilot Free in GitHub Codespaces: "No model available" after update, Auto selection, token isolation, and re-login

Offen
#4,405 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area:authentication area:models
Vorherrschende Sprache
Shell
Sterne
11.2k
Forks
1.9k
Ø Merge
14 Std. 16 Min.
Gemergte PRs (30 T.)
6

Beschreibung

### Describe the bug

GitHub Copilot CLI launches successfully in a GitHub Codespace, but every prompt immediately fails with:

```text
Execution failed: Error: No model available. Check policy enablement under GitHub Settings > Copilot
```

The account is on GitHub Copilot Free. GitHub's documentation states that Copilot CLI is available with all Copilot plans and that Copilot Free users should use Auto model selection.

The problem still occurs after all of the following:

- Updating Copilot CLI with `copilot update`
- Selecting Auto with `/model auto`
- Launching the CLI without the Codespaces-provided authentication environment variables
- Signing out and signing in again with `/logout` and `/login`

The screenshot taken before the update also shows `Remaining reqs.: 0%`. If the actual cause is an exhausted Free-plan request allowance, the current error message is misleading because it reports a model/policy problem instead of a usage-limit condition.

### Affected version

v1.0.78 after running `copilot update` (initially v1.0.3; the issue persists after updating)

### Steps to reproduce the behavior

1. Open a GitHub Codespace.
2. Run `copilot update`.
3. Launch Copilot CLI without the Codespaces token variables:

```bash
env -u COPILOT_GITHUB_TOKEN -u GH_TOKEN -u GITHUB_TOKEN -u COPILOT_MODEL copilot
```

4. Run `/logout`, then `/login`, and authenticate again with the Copilot Free account.
5. Run `/model auto`.
6. Enter a minimal prompt such as:

```text
Reply with "hello".
```

7. Observe the error:

```text
Execution failed: Error: No model available. Check policy enablement under GitHub Settings > Copilot
```

The same failure occurs both with the normal Codespaces environment and with the token variables removed for the Copilot process.

### Expected behavior

Copilot Free should either:

1. Respond using Auto model selection, because Copilot CLI is documented as available with all Copilot plans; or
2. If the Free-plan request allowance is exhausted, display a clear quota/usage-limit message.

It should not report that no model is available because of policy enablement when the user is on an individual Copilot Free plan and Auto is selected.

### Additional context

Environment:

- GitHub Codespaces
- VS Code integrated terminal
- Linux Codespace
- Copilot plan: Copilot Free
- Initial CLI version shown in the screenshot: v1.0.3
- Update offered in the screenshot: v1.0.78
- Updated with `copilot update`; the problem still reproduces
- `/model auto` does not resolve the problem
- Removing `COPILOT_GITHUB_TOKEN`, `GH_TOKEN`, `GITHUB_TOKEN`, and `COPILOT_MODEL` for the Copilot process does not resolve the problem
- Re-authenticating with `/logout` and `/login` does not resolve the problem
- The initial screenshot shows `Remaining reqs.: 0%`

Related older reports:

- https://github.com/github/copilot-cli/issues/635
- https://github.com/github/copilot-cli/issues/400

Screenshot of the exact terminal state and error:

GitHub Copilot CLI showing No model available in a Codespace terminal

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Reproduziere dies aus einem GitHub Codespace mit dem dokumentierten environment-unset copilot command und teste anschließend /logout, /login und /model auto, während du die gemeldeten verbleibenden Anfragen überprüfst. Verfolge den CLI-Pfad, der Antworten zur Modellverfügbarkeit oder zum Kontingent in „No model available“ umwandelt; abgeschlossen ist die Aufgabe, wenn Copilot Free entweder eine Antwort erhält oder eine klare Meldung über das Nutzungslimit ausgegeben wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github, shell
Bereich
cli
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
42/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.