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
Open a GitHub Codespace.
Run copilot update.
Launch Copilot CLI without the Codespaces token variables:
env -u COPILOT_GITHUB_TOKEN -u GH_TOKEN -u GITHUB_TOKEN -u COPILOT_MODEL copilot
Run /logout, then /login, and authenticate again with the Copilot Free account.
Run /model auto.
Enter a minimal prompt such as:
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:
- Respond using Auto model selection, because Copilot CLI is documented as available with all Copilot plans; or
- 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:

Describe the bug
GitHub Copilot CLI launches successfully in a GitHub Codespace, but every prompt immediately fails with:
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:
copilot update/model auto/logoutand/loginThe 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
Open a GitHub Codespace.
Run
copilot update.Launch Copilot CLI without the Codespaces token variables:
Run
/logout, then/login, and authenticate again with the Copilot Free account.Run
/model auto.Enter a minimal prompt such as:
Observe the error:
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:
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:
copilot update; the problem still reproduces/model autodoes not resolve the problemCOPILOT_GITHUB_TOKEN,GH_TOKEN,GITHUB_TOKEN, andCOPILOT_MODELfor the Copilot process does not resolve the problem/logoutand/logindoes not resolve the problemRemaining reqs.: 0%Related older reports:
Screenshot of the exact terminal state and error: