Issue: Copilot CLI AggregateError: Failed to list models

[EAGColab]

Describe the bug

I am unable to use the Copilot CLI behind a Zscaler corporate firewall. When running copilot, it fails immediately with Execution failed: AggregateError: Failed to list models.

Detailed investigation reveals a connect:errno=113 (No route to host) error when the CLI tries to reach api.business.githubcopilot.com. This appears to be caused by Zscaler interception creating a routing loop, as standard HTTPS traffic to github.com works fine.

Affected version

0.0.381

Steps to reproduce the behavior

Use an Ubuntu environment behind a Zscaler transparent proxy.

Run copilot.

Select any prompt or simply try to start the session.

Error occurs: ✗ Execution failed: AggregateError: Failed to list models.

Expected behavior

The CLI should be able to connect to the Copilot API, or provide clear configuration options to handle transparent proxy interception to avoid the routing loop.

Additional context

OS: Ubuntu (Hetzner Cloud)

Network: Zscaler Corporate Proxy

Troubleshooting attempted:

Lowered MTU to 1300 (no change).

Attempted setting NODE_EXTRA_CA_CERTS (no change, as connection fails before handshake).

curl and openssl to api.business.githubcopilot.com fail with No route to host.

Logs/Evidence:
openssl s_client -connect api.business.githubcopilot.com:443 output:

40275749FB7F0000:error:80000071:system library:BIO_connect:No route to host:../crypto/bio/bio_sock2.c:125:calling connect()
connect:errno=113

Traceroute shows a loop at Zscaler IP (132.147.112.106):

7 132.147.112.101 ...
8 132.147.112.106 ...
9 132.147.112.106 ...
...
30 132.147.112.101 ...

[andyfeller]

Thank you for raising this issue, @EAGColab! 🙇 At a glance, it seems like a combination of corporate firewalls and other errors are a problem here, which I want to dig into and unblock you.

Questions

1. Could you share any logs from copilot --log-level all --log-dir logs around the connection and model calls?