GitHub Copilot CLI
Copilot CLI errors and fixes
12 Copilot CLI error messages, quoted verbatim, each with what it means, why it happens and the fix documented in official docs, maintainer replies or release notes. Verified .
All Copilot CLI errors
- Status: Fixed in release8 fixed in release
- Status: By design1 by design
- Status: Open3 open
✗ No model available. Check policy enablement under GitHub Settings > CopilotCopilot 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."Status: Fixed in releaseYou are not authorized to use this Copilot feature, it requires an enterprise or organization policy to be enabled.The Copilot API refused the request because the Copilot CLI policy is not enabled, or not yet in effect, for the organization or enterprise that gives you Copilot.Status: By designRequest failed due to a transient API error. Retrying...A model request failed and the CLI is retrying it automatically. In the original report the retries ended with: "Sorry, you've hit a rate limit that restricts the number of Copilot model requests you can make within a specific time period. Please try again in 1 minute."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 errorThe CLI used up its five automatic retries for one model call. It often follows repeated "Response was interrupted due to a server error. Retrying..." lines. Other reports end with "Last error: CAPIError: 503 {"error":{"message":"HTTP/2 GOAWAY connection terminated","type":"connection_error"}}".Status: Fixed in releaseCAPIError: 400 {"message":"","code":"invalid_request_body"}The Copilot API rejected the request body the CLI sent for a model call.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."}}On the turn after a tool or function call, the API rejected the request because the same function-call item ID appeared twice in the input.Status: Open✗ Model call failed: "Connection error." ✗ Execution failed: CAPIError: Connection error.The CLI could not complete the chat completion call to the Copilot API.Status: Fixed in releaseposix_spawnp failureAfter long use, the bash tool can no longer start a new shell (pseudo-terminal), so every shell command fails.Status: Fixed in releaseServer failed to connectShown for Copilot Pro trial accounts as if it were a network error. The MCP logs showed the real API message: "Copilot Pro trials have been temporarily paused. Please upgrade your account or revert to Copilot Free".Status: Fixed in release✗ Error loading model list: Error: Not authenticatedAfter /resume of an existing session, /model could not list models because the resumed session had no authentication. New sessions worked.Status: Fixed in releaseError auto updating: Failed to fetch latest release: HttpError: API rate limit exceeded for 104.28.229.161. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)The update check used unauthenticated GitHub REST API calls and hit the per-IP rate limit, often on shared or NAT networks.Status: Fixed in releaseFailed to resume session: Error: Session file is corrupted (line 7103: SyntaxError: Unexpected token '', ""... is not valid JSON)The saved session transcript could not be parsed, so --resume or /resume refused to load it.Status: Fixed in release
New to Copilot CLI? Start with Copilot CLI in the tools directory.
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.