Browser reaches GitHub via Clash Verge Rev, but PowerShell/Git/npm/curl still time out—CLI tools often ignore system proxy. Prove the client works, then set shell proxies or enable Tun.
Ports: ports. Easier: Tun, Tun & AI.
Why the browser works but the CLI does not
| Tool | Reads system proxy? | Fix |
|---|---|---|
| Browser | Yes, usually | Already green |
| PowerShell | No | Set $env:HTTPS_PROXY (see below) |
| Git | No | git config http.proxy |
| npm | No | npm config set proxy |
PowerShell session
$env:HTTP_PROXY="http://127.0.0.1:PORT"
$env:HTTPS_PROXY="http://127.0.0.1:PORT"Prefer session/scripts over permanent user env vars that break when the port changes.
Git and npm
Set Git/npm proxy only when needed; unset for internal remotes. Cert errors: confirm the proxy path before blaming MITM.
Acceptance
- Connections show hits during git/npm.
- No hits → vars/Tun not applied.
- Hits but fail → node/target (latency).
Stop
Browser success ≠ CLI success. system proxy. Builds: download center.