How to Install Kimi CLI on Windows: PowerShell and UV Methods

Run the PowerShell command Invoke-RestMethod https://code.kimi.com/install.ps1 | Invoke-Expression to automatically install the UV package manager and Kimi CLI for Python 3.13 on Windows systems.

Kimi CLI (now branded as Kimi Code CLI) is MoonshotAI's command-line interface for interacting with Kimi AI models. According to the MoonshotAI/kimi-cli source code, the tool is distributed as a Python UV package, and Windows users can install it via a one-line PowerShell script that handles all dependencies.

Prerequisites for Installing Kimi CLI on Windows

Before running the installer, ensure your system meets the basic requirements. While the installation script handles most dependencies automatically, understanding the underlying technology helps troubleshoot potential issues.

System Requirements

Kimi CLI requires Python 3.13 for optimal performance, managed through UV, a fast, modern Python package manager written in Rust. The installation process will automatically download and configure UV if it is not already present on your system, placing the kimi executable in your PATH.

The fastest and most reliable method uses the official PowerShell installation script hosted at code.kimi.com. This approach mirrors the Unix installer logic found in [scripts/install.sh](/blob/main/scripts/install.sh) but is adapted for Windows environments in [scripts/install.ps1](/blob/main/scripts/install.ps1).

Open PowerShell and execute:

Invoke-RestMethod https://code.kimi.com/install.ps1 | Invoke-Expression

This command performs three critical operations:

  • Detects your Windows environment and downloads the appropriate UV installer
  • Installs UV locally if it is not already detected on your PATH
  • Executes uv tool install --python 3.13 kimi-cli to download and install the CLI

Method 2: Manual Installation with UV

If you already have UV installed on your Windows machine, you can bypass the PowerShell script and install Kimi CLI directly. This method is useful for developers who manage multiple Python tools through UV and want precise control over the installation environment.

Run the following command in your terminal:

uv tool install --python 3.13 kimi-cli

This command is identical to the one invoked by the automated installer at line 31 of [scripts/install.sh](/blob/main/scripts/install.sh#L31), ensuring consistency across platforms.

Verify Your Installation

After installation completes, confirm that the kimi command is accessible from your terminal. UV automatically places the executable in a directory included in your system PATH.

Run the verification command:

kimi --version

If the installation succeeded, this command returns the current version number of Kimi CLI. If you receive a "command not found" error, restart your terminal session to refresh the environment variables.

Upgrade or Uninstall Kimi CLI on Windows

The MoonshotAI/kimi-cli repository provides straightforward commands for lifecycle management through UV, documented in [docs/en/guides/getting-started.md](/blob/main/docs/en/guides/getting-started.md#L66-L75).

To upgrade to the latest release while bypassing the local cache:

uv tool upgrade kimi-cli --no-cache

To completely remove Kimi CLI from your system:

uv tool uninstall kimi-cli

These commands ensure that your Windows installation remains current with the latest features and security updates published to the Python Package Index.

First Run and Configuration

Once installed, navigate to your project directory and invoke the interactive AI session by typing kimi. On first launch, the CLI prompts you to configure an LLM provider using the /login slash command, as detailed in the official guide at lines 77-92 of [docs/en/guides/getting-started.md](/blob/main/docs/en/guides/getting-started.md#L77-L92).

Summary

  • Use the PowerShell one-liner Invoke-RestMethod https://code.kimi.com/install.ps1 | Invoke-Expression for automated installation of Kimi CLI on Windows.
  • UV is required but installed automatically by the script; manual installers can run uv tool install --python 3.13 kimi-cli directly.
  • Verify installation by running kimi --version after installation completes.
  • Manage the tool using uv tool upgrade kimi-cli --no-cache for updates and uv tool uninstall kimi-cli for removal.
  • Configuration happens interactively on first run via the /login command.

Frequently Asked Questions

Can I install Kimi CLI on Windows without using PowerShell?

While PowerShell provides the most streamlined experience via [scripts/install.ps1](/blob/main/scripts/install.ps1), you can manually install UV from the official Astral website, then run uv tool install --python 3.13 kimi-cli in any Windows terminal that supports UV, including Command Prompt or Windows Terminal.

What Python version does Kimi CLI require on Windows?

The installation targets Python 3.13 specifically, as defined in the installation scripts and [pyproject.toml](/blob/main/pyproject.toml). The UV tool ensures this version is used even if you have other Python installations on your system.

How do I update Kimi CLI to the latest version on Windows?

Run the command uv tool upgrade kimi-cli --no-cache in your terminal. This command fetches the latest release from the Python Package Index and updates your local installation, bypassing any cached versions that might interfere with the update.

Where is the Kimi CLI executable installed on Windows?

UV places the kimi.exe executable in its default tools directory, typically located at %USERPROFILE%\.local\bin or within the UV installation path. The installer automatically adds this location to your system PATH, making the command available in new terminal sessions.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →