
Kimi CLI Review, Pricing & Alternatives (2026)
A retired Python terminal agent replaced by Kimi Code CLI
rebranded: Kimi CLI was archived after final release 1.52.0 on September 22, 2026. Moonshot AI replaced it with Kimi Code CLI, which remains actively developed.
Last updated: October 26, 2026
What is Kimi CLI?
Kimi CLI was Moonshot AI’s open-source Python terminal agent for inspecting code, editing files, running commands, and connecting MCP tools. It suited developers who wanted a conversational coding shell, but its repository is now archived and receives no fixes. The software was free under Apache-2.0, while current Kimi Code access starts at $19/month through Kimi membership.
Kimi CLI was Moonshot AI’s open-source Python terminal coding agent, released in 2025 for developers who wanted conversational repository work. It accepted a project directory as working context and used the Kimi model family to inspect code, edit files, run commands, and connect external tools through MCP. Its Apache-2.0 GitHub repository accumulated more than 11,000 stars and 1,300 forks, giving the project meaningful visibility among terminal coding tools. The application is now archived after final release 1.52.0 on September 22, 2026, so it is a discontinued implementation rather than a maintained deployment choice. Moonshot replaced it with Kimi Code CLI, a separate Node.js project with a native binary and redesigned interface. Existing users can migrate configuration and selected sessions, but Kimi CLI receives no further releases, bug fixes, or security updates.
Kimi CLI operated as a terminal REPL for repository work. A developer points it at a project directory, then asks the agent to inspect code, explain files, draft or apply edits, run shell commands, and handle command failures in later turns. Skills and plugins added reusable capabilities, while MCP connected external tools and services. Approval controls allowed review of commands and file changes before execution, with more automated modes available when broader authorization was acceptable. The client used Kimi models or compatible configured providers, so it was not a standalone model API. Migration to Kimi Code transfers config.toml, MCP server settings, input history, and selected sessions. OAuth credentials, MCP authorizations, and legacy plugins require separate setup, meaning migration preserves useful project context without carrying every authentication state into the replacement.
Kimi CLI’s technology story ends with release 1.52.0 on September 22, 2026, after version 1.51.0 archived the repository and packages, stopped the PyPI installation path, and redirected users to Kimi Code CLI. The replacement changes the implementation from Python and uv to Node.js, includes a native binary, and redesigns the terminal interface. Kimi Code supports code reading, file editing, command execution, web search, and multi-file engineering tasks. Migration can transfer config.toml, MCP server settings, input history, and selected sessions, although OAuth credentials, MCP authorizations, and legacy plugins require separate setup. The service also separates Kimi membership from the Kimi Platform API: membership bundles coding access, while the API bills tokens on demand. Kimi CLI remains source code, not a general model API.
Kimi Code access is bundled with international Kimi membership rather than sold as a separate CLI license. The archived Kimi CLI software costs $0 under Apache-2.0, but running an agent still requires a configured provider or Kimi service, so the license does not cover inference. Current membership starts at Plus for $19 per month or $180 annually, followed by Pro at $39 monthly or $372 annually, Max at $99 or $948 annually, and Ultra at $199 or $1,908 annually. Plus and higher include Kimi Code, share one monthly credit pool across included features, and use a rolling five-hour limit instead of the former weekly limit. Credits do not roll over. The new Go tier has no Kimi Code quota, while Kimi Platform API requests remain separately metered by tokens.
Archival status is the decisive limitation: Kimi CLI ended with release 1.52.0 on September 22, 2026, and receives no security maintenance, bug fixes, or new releases. Its Apache-2.0 code remains available for study, modification, and redistribution, but older authentication or provider behavior may fail. Claude Code, Gemini CLI, and Qwen Code are maintained alternatives, while Kimi Code CLI is the direct replacement for Moonshot users. Kimi Code is a Node.js successor with a redesigned terminal interface and native binary, and migration transfers config.toml, MCP server settings, input history, and selected sessions. Login credentials, MCP authorizations, and legacy plugins require separate setup. Kimi Code membership starts at $19/month for Plus, while Go has no coding quota. Choose Kimi Code for current Moonshot access, or Claude Code, Gemini CLI, or Qwen Code for active maintenance and broader provider choice.
Who is Kimi CLI best for?
- Developers studying or preserving an older Moonshot terminal-agent implementation.
- Teams migrating Kimi CLI configuration and sessions to Kimi Code.
- Kimi members wanting terminal access to Moonshot coding models.
- Engineers comfortable reviewing agent commands and file changes.
Kimi CLI Pricing (2026)
Pricing model: Freemium. All prices in USD.
| Plan | Price | What you get |
|---|---|---|
| Legacy CLI software | $0 | The source is Apache-2.0. The archived application receives no fixes or security updates, and model access requires a configured provider or Kimi service. |
| Kimi membership Plus | $19/month | Includes Kimi Code, a shared monthly credit pool, and a rolling five-hour usage limit. Annual billing is $180. |
| Kimi membership Pro | $39/month | Includes Kimi Code with a larger shared allowance. Annual billing is $372. |
| Kimi membership Max | $99/month | Includes Kimi Code with larger credits and higher access than Pro. Annual billing is $948. |
| Kimi membership Ultra | $199/month | Includes Kimi Code with the largest published membership allowance. Annual billing is $1,908. |
Pros and Cons
Pros
- Apache-2.0 licensing permits reuse and modification of the archived code.
- The agent combines code reading, editing, shell execution, and MCP tools.
- Migration transfers configuration, history, and selected sessions.
- Kimi Code provides a native Node.js successor with an updated terminal interface.
Cons
- The original repository is archived and receives no security updates.
- Login credentials and MCP authorizations do not migrate.
- Kimi Code usage shares credits across included membership features.
Who should look elsewhere?
- New production deployments requiring security maintenance.
- Users seeking a standalone, metered coding API from the CLI.
- Users needing a maintained Python terminal package.
Technical Details
Frequently Asked Questions
Is Kimi CLI still maintained?
No. Moonshot archived the Python repository and published 1.52.0 as the final release on September 22, 2026. The project has no planned bug fixes, security updates, or further releases. Moonshot directs users to Kimi Code CLI. Its migration command can import configuration, MCP settings, input history, and selected sessions, but users must log in again and reauthorize MCP services.
How much does Kimi CLI cost?
The archived software is free under Apache-2.0, but using an agent still requires model access. Current Kimi Code access is bundled with membership. International plans start at Plus for $19 per month, followed by Pro at $39, Max at $99, and Ultra at $199. The Go tier has no Kimi Code quota.
Kimi CLI or Claude Code?
Kimi CLI is archived, while Claude Code remains an actively maintained competing terminal agent. Kimi Code is the relevant Moonshot comparison because it replaces the Python project and supports migration. Claude Code suits teams already using Anthropic subscriptions and tooling. Kimi Code suits users selecting Moonshot membership and its shared coding-service access.
Does Kimi CLI train on user data?
The archived client documentation does not define one universal training policy. Data handling depends on the model or hosted service receiving prompts, files, command output, and tool calls. Users should review the applicable Kimi service terms and privacy controls. Organizations should avoid sending secrets to an agent or provider without reviewing retention and training settings.
Can I use Kimi CLI commercially?
The repository code is released under Apache-2.0, which permits commercial use, modification, and redistribution subject to the license and notices. That permission covers the software, not model-provider terms, trademarks, hosted-account rules, or third-party dependencies. Commercial users should migrate to the maintained successor and review its current service terms before deployment.
Best Kimi CLI Alternatives in 2026
These tools do the same job as Kimi CLI, with different pricing, limits and trade-offs.
An agentic coding assistant for terminal, IDE, desktop, and web

An open source Gemini agent for coding and research in the terminal

Terminal coding agent with sandbox controls and OpenAI model access

Open-source terminal agent with hosted and local model support