How to Update Kimi-CLI to the Latest Version: 4 Methods Explained

Run pip install -U kimi-cli to upgrade to the latest stable release from PyPI, or use uv pip install -U kimi-cli if you have the uv toolchain installed.

Keeping your command-line interface current ensures access to the latest features and security patches. Since Kimi-CLI is distributed as a standard Python package maintained by MoonshotAI, updating it follows standard Python packaging workflows. This guide covers every method to update kimi-cli to the latest version, from simple pip commands to building from source.

Update Kimi-CLI to the Latest Version Using pip

The most straightforward way to update kimi-cli to the latest version is using pip, Python's default package manager. The package metadata, including the current version number, is declared in the repository's pyproject.toml file.

pip install -U kimi-cli

The -U (or --upgrade) flag instructs pip to fetch the newest release from PyPI and replace the existing installation. This method works across all platforms where Python is installed and is the recommended approach for most users.

Upgrade Using uv (Recommended for Speed)

For users who have adopted the uv toolchain—the modern, fast Python package manager used by the Kimi-CLI project itself—upgrading is equally simple but significantly faster.

uv pip install -U kimi-cli

The repository's Makefile demonstrates that the development workflow relies on uv for dependency management. The make prepare target runs uv sync to align the lockfile with declared dependencies, while make install executes uv pip install -e . to install the package in editable mode during development.

Upgrade Using Homebrew (macOS)

If you installed Kimi-CLI via Homebrew on macOS, use the package manager's native upgrade command rather than pip. Homebrew pulls the latest release directly from the GitHub repository.

brew upgrade kimi-cli

This method keeps your installation managed within the Homebrew ecosystem, avoiding conflicts between pip and Homebrew-managed packages.

Upgrade from Source (Development Builds)

Contributors or users needing specific commits not yet released to PyPI can update kimi-cli to the latest version by building from source. This method uses the Makefile targets defined in the MoonshotAI/kimi-cli repository.

git pull origin main          # Get the latest code

make prepare                  # Install/refresh dependencies

make install                  # Install the package into the current environment

The make install target runs uv pip install -e ., installing the package in editable mode so changes to the source code reflect immediately without reinstallation. The entry point for the CLI is located in src/kimi_cli/cli/__main__.py.

Verify Your Installation

After updating, confirm you are running the latest version by checking the version string. The CLI reads this from pyproject.toml via the core application bootstrap in src/kimi_cli/app.py.

kimi --version

Expect output showing the current release (e.g., 0.70.0), which corresponds to the version badge displayed in the README and validated by scripts/check_version_tag.py in the CI pipeline.

Updating the package does not affect your existing configuration or session data. Kimi-CLI automatically migrates old settings when needed, as documented in the repository's migration notes.

Summary

• Use pip install -U kimi-cli for standard PyPI upgrades across all platforms
• Use uv pip install -U kimi-cli for faster upgrades if you use the uv toolchain
• Use brew upgrade kimi-cli on macOS for Homebrew-managed installations
• Build from source using make prepare and make install for development versions
• Verify updates with kimi --version, which reads from pyproject.toml via src/kimi_cli/app.py

Frequently Asked Questions

Will updating kimi-cli delete my chat history or configuration files?

No. Updating kimi-cli to the latest version preserves all existing configuration and session data. The application automatically migrates settings when necessary, ensuring a seamless transition between versions without manual intervention.

How do I know if I'm running the latest version of kimi-cli?

Run kimi --version in your terminal. The output displays the installed version, which you can compare against the latest release shown in the GitHub repository's README badge or the version field in pyproject.toml. The CI pipeline uses scripts/check_version_tag.py to ensure Git tags match this version field.

Can I use both pip and Homebrew to manage kimi-cli installations?

You should not mix package managers for the same installation. If you initially installed via Homebrew, continue using brew upgrade kimi-cli. If you used pip, stick with pip install -U kimi-cli. Mixing managers can lead to path conflicts and version inconsistencies that prevent the kimi command from functioning correctly.

What if the kimi command is not found after updating?

This usually indicates a PATH issue where the new installation location differs from the old one. Ensure your shell's PATH includes the Python binary directory (often ~/.local/bin for pip user installs or the Homebrew bin directory). You may need to restart your terminal session after upgrading for the changes to take effect.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}