GitHub Copilot CLI error
Copilot CLI: No model available. Check policy enablement under GitHub Settings...
✗ No model available. Check policy enablement under GitHub Settings > CopilotStatus: Fixed in releaseLast verified 4 documented fixes4 sources
What it means
Copilot CLI could not get any usable model for your account. Maintainers said the message "can appear for a variety of reasons that basically boil down to problems retrieving models."
Causes
- Copilot Individual users: per maintainer andyfeller, "Copilot Individual users ... had unconfigured or disabled models excluded from the list."
- Copilot Business and Enterprise users: "still governed by policies set by organization and enterprise owners". Several reporters in the thread found Copilot CLI turned off in their organization's Copilot policy.
- In #552 the maintainer said that "the controls and policies associated with you were cached with GitHub Copilot CLI being unconfigured / disabled", and later that there is "a more complex problem on the GitHub.com side".
- Copilot Individual plans only get a subset of supported models (maintainer comment linking the supported-models-per-plan docs).
How to fix it
- Fix 1.
Upgrade to v0.0.372 or later. That release "introduces support for Copilot Individual users to see and enable models within the
copilot" (andyfeller, #400). - Fix 2.
Business/Enterprise: an org or enterprise owner must enable the Copilot CLI policy and the models you need. Check which models and features are enabled for you in your Copilot settings.
Snippethttps://github.com/settings/copilot/features - Fix 3.
If it still happens on the latest version, maintainers asked for logs and a new issue:
Terminalcopilot --log-level all --log-dir logs - Fix 4.
v1.0.10 changelog: "Model picker reorganizes models into Available, Blocked/Disabled, and Upgrade tabs based on user plan and policy".
More Copilot CLI errors
All 12 Copilot CLI errorsYou are not authorized to use this Copilot feature, it requires an enterprise or organization policy to be enabled.Status: By designRequest failed due to a transient API error. Retrying...Status: Open✗ Execution failed: Error: Failed to get response from the AI model; retried 5 times (total retry wait time: 5.927545045390875 seconds) Last error: Unknown errorStatus: Fixed in releaseCAPIError: 400 {"message":"","code":"invalid_request_body"}Status: OpenExecution failed: CAPIError: 400 {"error":{"code":"bad_request","type":"websocket_error","message":"Duplicate item found with id fc_call_ikBrgmi06fcJeO6uIpJJEQbJ. Remove duplicate items from your input and try again."}}Status: Open✗ Model call failed: "Connection error." ✗ Execution failed: CAPIError: Connection error.Status: Fixed in releaseposix_spawnp failureStatus: Fixed in releaseServer failed to connectStatus: Fixed in release
Related reading
- GitHub Copilot SDK Hits GA: Embed the Copilot Agent Runtime in Your Own AppsGitHub Copilot SDK is generally available: embed the Copilot agent runtime in your apps across six languages. What changed at GA and what it means for builders.
- Claude Code vs Codex vs Copilot CLI: Local Sandboxes ComparedCopilot CLI local sandboxing is GA. How it compares with Claude Code and Codex on defaults, network, credentials, Windows, and what still runs outside.
- GitHub Copilot CLI With Ollama: Local Models and the New SandboxCopilot CLI 1.0.94 finds local Ollama models from /model and ships an OS-level sandbox. Setup, the 4k context trap, and why local is not offline.
- Claude Sonnet 5.5 Developer Guide: Pricing and API ChangesClaude Sonnet 5.5 costs $2/$10 per million tokens, and cache reads fell to $0.10 on October 7 - half of Opus 5.5 on every line. Pricing math and API changes.
- GitHub Copilot's September Reset: Prepaid Seats, One Unified Agent Experience, Balanced Reviews by DefaultGitHub Copilot September changes: prepaid Business and Enterprise seats, one unified agent experience and Balanced reviews by default. What it means for teams.
- GitHub's August 17 Outage: Agent Fleets Need a 4-Hour Local FallbackGitHub's August 17 outage ran 7 hours 47 minutes across PRs, Actions, APIs and Copilot. Why coding agent fleets need a four-hour local fallback.
FAQ
What does "No model available. Check policy enablement under GitHub Settings..." mean in Copilot CLI?
Copilot CLI could not get any usable model for your account. Maintainers said the message "can appear for a variety of reasons that basically boil down to problems retrieving models."
How do I fix "No model available. Check policy enablement under GitHub Settings..."?
There are 4 documented fixes. Start with the first: Upgrade to v0.0.372 or later. That release "introduces support for Copilot Individual users to see and enable models within the copilot" (andyfeller, #400).
Is this Copilot CLI error fixed?
Status: Fixed in release. A release fixed this. The affected versions note says where the fix landed. Affected versions: Reported from 0.0.331 through 0.0.361 (users reported 0.0.330 working). The model enablement fix shipped in 0.0.372.
Sources
Last verified against 4 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.