What version of Kimi Code CLI is running?
None (installation is blocked before CLI can be installed)
Which open platform/subscription were you using?
None
Which model were you using?
N/A
What platform is your computer?
windows, linux and macOS
What issue are you seeing?
Both the Linux (install.sh) and Windows (install.ps1) installation scripts bootstrap uv by fetching the official uv installer from https://astral.sh/uv/install.sh (or install.ps1). However, the astral.sh installer ultimately downloads the uv binary from GitHub Releases (github.com/astral-sh/uv/releases/download/...).
In network environments where GitHub is blocked or severely throttled (e.g. mainland China behind the GFW), this step silently hangs or fails, causing the entire Kimi CLI installation to abort.
What steps can reproduce the bug?
Linux / macOS
curl -LsSf https://code.kimi.com/install.sh | bash
The script calls curl -fsSL https://astral.sh/uv/install.sh | sh, which then tries to download from github.com and eventually times out or errors out.
Windows (PowerShell)
irm https://code.kimi.com/install.ps1 | iex
The script calls Invoke-RestMethod https://astral.sh/uv/install.ps1, which has the same dependency on GitHub Releases.
What is the expected behavior?
- The installation scripts should either:
- Support an environment variable (e.g.
KIMI_UV_INSTALL_URL or UV_INSTALL_URL) so users can point to a mirror / pre-downloaded uv binary, or
- Document an offline / mirror-based installation path for users who cannot reach GitHub.
- Alternatively, the scripts could detect a network failure when downloading uv and print a helpful message telling the user how to manually install uv from a mirror before re-running the installer.
Additional information
- The
astral.sh installer itself is not the bottleneck; the bottleneck is the subsequent GitHub Release asset download.
uv provides standalone binaries and alternative install methods. Users in restricted regions can often obtain uv via domestic mirrors (e.g. Tsinghua TUNA, USTC, etc.) or by pre-downloading the binary. The current install.sh / install.ps1 offer no hook to skip or replace the uv bootstrap step.
What version of Kimi Code CLI is running?
None (installation is blocked before CLI can be installed)
Which open platform/subscription were you using?
None
Which model were you using?
N/A
What platform is your computer?
windows, linux and macOS
What issue are you seeing?
Both the Linux (
install.sh) and Windows (install.ps1) installation scripts bootstrap uv by fetching the official uv installer from https://astral.sh/uv/install.sh (orinstall.ps1). However, the astral.sh installer ultimately downloads the uv binary from GitHub Releases (github.com/astral-sh/uv/releases/download/...).In network environments where GitHub is blocked or severely throttled (e.g. mainland China behind the GFW), this step silently hangs or fails, causing the entire Kimi CLI installation to abort.
What steps can reproduce the bug?
Linux / macOS
curl -LsSf https://code.kimi.com/install.sh | bashThe script calls
curl -fsSL https://astral.sh/uv/install.sh | sh, which then tries to download from github.com and eventually times out or errors out.Windows (PowerShell)
irm https://code.kimi.com/install.ps1 | iexThe script calls
Invoke-RestMethod https://astral.sh/uv/install.ps1, which has the same dependency on GitHub Releases.What is the expected behavior?
KIMI_UV_INSTALL_URLorUV_INSTALL_URL) so users can point to a mirror / pre-downloaded uv binary, orAdditional information
astral.shinstaller itself is not the bottleneck; the bottleneck is the subsequent GitHub Release asset download.uvprovides standalone binaries and alternative install methods. Users in restricted regions can often obtain uv via domestic mirrors (e.g. Tsinghua TUNA, USTC, etc.) or by pre-downloading the binary. The currentinstall.sh/install.ps1offer no hook to skip or replace the uv bootstrap step.