copilot cli returns: AggregateError: Failed to list models

Describe the bug

I am trying to use copilot cli enterprise. I have successfully logged in but after that none of the commands are working:

● Welcome snagaman_cisco!

● GitHub MCP Server: Connected

✗ Execution failed: AggregateError: Failed to list models

/model results in

Select Model

Choose the AI model to use for Copilot CLI. The selected model will be persisted and used for future sessions.

Error loading model list: AggregateError: Failed to list models

Some models are not available. For information on Copilot policies and subscription, visit: https://github.com/settings/copilot/features

I am running this from WSL2 (5.15.167.4-microsoft-standard-WSL2) on WINDOWS 11

The same thing is working from my VS CODE as plugin perfectly. This VS Code is being from WSL env.

Regards
Sai

Affected version

0.0.391 Commit: e5c18e1

Steps to reproduce the behavior

copilot

/model

Expected behavior

No response

Additional context

WSL2 (5.15.167.4-microsoft-standard-WSL2) on WINDOWS 11 Enterprise

Github: please provide better error messages. There are way more errors than you think.

GitHub Copilot v0.0.395 on Linux also has this problem, just by attempting to list models with /model or /models

2026-01-27T08:46:29.979Z [ERROR] Starting remote MCP client for github-mcp-server with url: https://api.individual.githubcopilot.com/mcp/readonly
2026-01-27T08:46:29.979Z [ERROR] Creating MCP client for github-mcp-server...
2026-01-27T08:46:29.981Z [ERROR] Connecting MCP client for github-mcp-server...
2026-01-27T08:46:30.245Z [ERROR] MCP transport for github-mcp-server closed
2026-01-27T08:46:30.245Z [ERROR] Failed to start MCP client for remote server github-mcp-server: TypeError: fetch failed
2026-01-27T08:46:30.245Z [ERROR] GitHub MCP server configured after authentication

using vpn solved the issue

having the same problem on v0.0.400

@variable

@variable , the @fcat97 user reported that using a VPN is a workaround. Can you try to confirm? I do not like that kind of workaround, nor that policy to filter per IP address, though...

@variable , the @fcat97 user reported that using a VPN is a workaround. Can you try to confirm? I do not like that kind of workaround, nor that policy to filter per IP address, though...

I don't understand how VPN has anything to do with this.

Agreed, VPNs don't come in to the picture.

Could Copilot CLI start by providing better error messages?

Simple stuff like: HTTP method, URL, response code (if any), response body (if any), etc.

Telling us the models are not available, or that it's a policy issue, is completely wrong.

For me, when I directly connect to Wi-Fi, it works. But if I connect with Android Hotspot, it doesn't. But using VPN with Android Hotspot, it works again. Weird I know!

I'm using copilot on Ubuntu 25.10

+1

خترق

I'm also having the issue with version v0.0.403

And the logs:

2026-02-05T14:32:11.034Z [ERROR] Starting remote MCP client for github-mcp-server with url: https://api.business.githubcopilot.com/mcp/readonly
2026-02-05T14:32:11.034Z [ERROR] Creating MCP client for github-mcp-server...
2026-02-05T14:32:11.037Z [ERROR] Connecting MCP client for github-mcp-server...
2026-02-05T14:32:11.037Z [DEBUG] Creating copilot-client for integration ID copilot-developer-cli with token authentication. User-agent: copilot/0.0.403 (darwin v24.11.1) term/vscode
2026-02-05T14:32:11.280Z [INFO] No update needed, current version is 0.0.403, fetched latest release is v0.0.403
2026-02-05T14:32:11.451Z [DEBUG] Failed to initialize tools for validation: Error: Failed to list models: 403
2026-02-05T14:32:11.795Z [ERROR] MCP client for github-mcp-server connected, took 758ms
2026-02-05T14:32:11.796Z [ERROR] MCP server github-mcp-server provided instructions: The GitHub MCP Server provides tools to interact with GitHub platform.

Not sure what is happening, tried vpn, no vpn, wifi, hotspot nothing is working.
I have a pro subscription with cli enabled.
Thanks

I had the same problem in MacOS, directly connecting to internet, faced with the following error

Signed in successfully as You can now use Copilot.

Select Model

Choose the AI model to use for Copilot CLI. The selected model will be persisted and used for future sessions.

Error loading model list: AggregateError: Failed to list models

Some models are not available. For information on Copilot policies and subscription, visit: https://github.com/settings/copilot/features

Search models...

I'm now experiencing the same error with v0.0.406. This on a Windows 11 machine using Powershell 7.5.4 in Windows Terminal.

Might have the answer.

Could be an IPv6 issue.

For me, everything worked fine until I paired with my phone.

Trying to diagnose further, the API lookup over IPv6 failed

echo This works
curl -4 -I https://api.github.com
echo This fails
curl -6 -I https://api.github.com

When I disabled IPv6 through sysctl, and it then works (both ping commands), and the models return. Logging in always worked.

Fully admit, I don't know why this solution works. According to AI:

  - Those Copilot endpoints (api.*.githubcopilot.com, plus GitHub API calls) publish AAAA (IPv6) and A (IPv4) records.
  - On your tether, WSL had some IPv6 plumbing (an IPv6 address and even a default IPv6 route), but the upstream path
    was effectively unusable or inconsistent.
  - Node’s HTTP client (Copilot CLI is Node) will often try the IPv6 address first (or try multiple addresses and
    collect failures). When IPv6 is “present but broken”, you get slow timeouts / multiple connection failures, and Node
    can surface that as an AggregateError after retries.
  - Disabling IPv6 forces everything onto IPv4, so those requests stop hitting the broken path.

Might have the answer.

Could be an IPv6 issue.

For me, everything worked fine until I paired with my phone.

Trying to diagnose further, the API lookup over IPv6 failed
echo This works
curl -4 -I https://api.github.com
echo This fails
curl -6 -I https://api.github.com
When I disabled IPv6 through sysctl, and it then works (both ping commands), and the models return. Logging in always worked.

Fully admit, I don't know why this solution works. According to AI:
  - Those Copilot endpoints (api.*.githubcopilot.com, plus GitHub API calls) publish AAAA (IPv6) and A (IPv4) records.
  - On your tether, WSL had some IPv6 plumbing (an IPv6 address and even a default IPv6 route), but the upstream path
    was effectively unusable or inconsistent.
  - Node’s HTTP client (Copilot CLI is Node) will often try the IPv6 address first (or try multiple addresses and
    collect failures). When IPv6 is “present but broken”, you get slow timeouts / multiple connection failures, and Node
    can surface that as an AggregateError after retries.
  - Disabling IPv6 forces everything onto IPv4, so those requests stop hitting the broken path.

My IPV6 works fine with api.github.com, still having the same model list problem.

+1

It suddenly worked fine for a day, then the next day I tried to use it again, I started having "Error loading model list: Error: Failed to list models"

The tool is too unstable to use.

I have the same issue with preRelease version GitHub Copilot CLI 0.0.417 on my MacOS
Hmm, has the solution been found yet?

updated: on macOS use workaround in this ticket #1104 works for me!

I had the same issue, and running this command NODE_TLS_REJECT_UNAUTHORIZED=0 copilot solved that issue, temporarily. But with some bash alias alias copilot="NODE_TLS_REJECT_UNAUTHORIZED=0 copilot", you can make it definitive. Not a clean fix, but it worked in my case.

First, I want to apologize for such a late follow up here especially as this is an understandably frustrating experience. 🙇

I would love to follow up with anyone here who is continuing to have problems with latest 1.0.x release since several efforts since GA to improve this experience including:

/model picker has been revamped to provide more information about models unavailable due to policy or plan
retrieving models from Copilot API has been made more resilient

Beyond this, we have recognize there are several different network and SSL/TLS factors that have impacted users:

Are you in a corporate environment with firewall rules around subscription based routes?
Do you have custom SSL/TLS certificates in your system store that conflict with Mozilla CA bundle?
Is this a product bug that updating to a newer version will fix?

@andyfeller

@andyfeller I am still experiencing this issue on the latest 1.0.40 release.
I am running GitHub Copilot CLI on a Windows Server 2022 virtual machine which is behind a corporate firewall, however I don't know the details of that firewall's setup, and can confirm that the copilot extensions for VS, VSCode, Neovim, and SSMS work as expected.
We use self-signed TLS certificates which may conflict with Mozilla CA bundle. This has caused issues in the past with unrelated services such as cargo.

I don't receive any error when launching the Copilot CLI, however when I attempt to prompt I receive:

✗ Execution failed: Error: Failed to list models

Likewise, when executing /model, I receive:

✗ Error loading model list: Error: Failed to list models

Navigation Menu

Repository navigation

copilot cli returns: AggregateError: Failed to list models #1081

Describe the bug

Affected version

Steps to reproduce the behavior

Expected behavior

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

copilot cli returns: AggregateError: Failed to list models #1081

Description

Describe the bug

Affected version

Steps to reproduce the behavior

Expected behavior

Additional context

Activity

credmond commented on Jan 26, 2026

rakotomandimby commented on Jan 27, 2026

rakotomandimby commented on Jan 27, 2026

fcat97 commented on Jan 29, 2026

variable commented on Feb 1, 2026

rakotomandimby commented on Feb 2, 2026

variable commented on Feb 3, 2026

credmond commented on Feb 3, 2026

fcat97 commented on Feb 3, 2026

Ayyoub-Ka commented on Feb 4, 2026

shskol92-create commented on Feb 4, 2026

mogaleaf commented on Feb 5, 2026

sg-victorchai commented on Feb 8, 2026

Tjeerd-menno commented on Feb 9, 2026

teh-hippo commented on Feb 10, 2026

variable commented on Feb 10, 2026

GuilhermeYm commented on Feb 16, 2026

variable commented on Feb 22, 2026

quangnguyenbh commented on Feb 25, 2026

quangnguyenbh commented on Feb 25, 2026

Quentin-Gillet commented on Mar 6, 2026

andyfeller commented on Apr 9, 2026

dylanrenwick commented on May 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions