github / github/copilot-cli

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

Open
#4,405 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:authentication area:models
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the bug

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

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:

    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:

    Reply with "hello".
    
  7. Observe the error:

    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:

Screenshot of the exact terminal state and error:

GitHub Copilot CLI showing No model available in a Codespace terminal

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce from a GitHub Codespace with the documented environment-unset copilot command, then test /logout, /login, and /model auto while checking the reported remaining requests. Trace the CLI path that turns model availability or quota responses into “No model available”; done means Copilot Free either receives a response or gets a clear usage-limit message.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, shell
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.