GitHub Copilot CLI error
Copilot CLI: Model call failed: "Connection error."
✗ Model call failed: "Connection error."
✗ Execution failed: CAPIError: Connection error.Status: Fixed in releaseLast verified 2 documented fixes3 sources
What it means
The CLI could not complete the chat completion call to the Copilot API.
Causes
- A regression in 0.0.374. Release note for 0.0.375: "Fix 'Connection Error' issues due to subscription-based route used in chat completions".
- Earlier reports (0.0.331 to 0.0.337) involved business accounts being sent to the individual endpoint. Staff later said the /models endpoint "gained retry logic and subscription route fallbacks that fix the business-vs-individual endpoint misrouting".
How to fix it
- Fix 1.
Upgrade to 0.0.375 or later. Maintainer devm33: "The fix here is now available in stable release 0.0.375."
- Fix 2.
devm33 also said that from the next release,
--no-auto-update"will only run the version shipped with the binary", so pinning a version no longer needs ~/.copilot/pkg cleared by hand.Terminalcopilot --no-auto-update
More Copilot CLI errors
All 12 Copilot CLI errors✗ No model available. Check policy enablement under GitHub Settings > CopilotStatus: Fixed in releaseYou 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: Openposix_spawnp failureStatus: Fixed in releaseServer failed to connectStatus: Fixed in release
Related reading
- 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.
- GitHub Copilot for JetBrains Gains Persistent Memory and Ollama BYOKGitHub Copilot for JetBrains adds memory across chat sessions, Ollama as a BYOK provider, and enterprise settings for MCP access. What each feature does.
FAQ
What does "Model call failed: "Connection error."" mean in Copilot CLI?
The CLI could not complete the chat completion call to the Copilot API.
How do I fix "Model call failed: "Connection error.""?
There are 2 documented fixes. Start with the first: Upgrade to 0.0.375 or later. Maintainer devm33: "The fix here is now available in stable release 0.0.375."
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: 0.0.374 (regression). Fixed in 0.0.375 (2026-01-07).
Sources
Last verified against 3 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.