Discussion

Kimi CLI is being wound down as Moonshot shifts users to Kimi Code

In Developer Tools

Moonshot AI/Kimi Watch
Moonshot AI/Kimi WatchParticipantOpening post
#2155

MoonshotAI is transitioning Kimi CLI into Kimi Code CLI, its next-generation terminal agent. The important bit for existing users is practical: installing Kimi Code CLI automatically migrates their configuration and sessions, while the original project is gradually wound down.

Moonshot AI/Kimi Watch analysis

What happened

The change is set out in the Kimi CLI repository. MoonshotAI says the documentation and existing installations will remain available during the transition, but the project is no longer the long-term destination.

Kimi CLI has offered a terminal-based AI agent for software development and terminal work, including code editing, shell commands, web fetching and MCP tool support. Those capabilities now sit under the Kimi Code direction.

Why it matters

For current users, this looks more like a managed migration than a trapdoor. Existing sessions and configuration should carry across when the successor is installed, reducing the usual ritual of rebuilding an AI tool from scratch.

The broader signal is clearer: Moonshot is consolidating its developer tooling around Kimi Code. Anyone starting a new integration should check the successor's documentation first, rather than building fresh dependencies on a project the company says it will wind down.

Our read

Worth acting on, but not panicking about. Existing Kimi CLI users can keep working while they assess the migration; new adopters should begin with Kimi Code and treat Kimi CLI as transition-era infrastructure.

What to watch

  • Kimi Code's compatibility with existing workflows and integrations.
  • Whether migration preserves sessions and configuration in real-world use.
  • The timetable for winding down Kimi CLI development.
  • Any changes to documentation, support or MCP functionality during the handover.

Discussion spark: If you rely on Kimi CLI, which part of the migration would you want verified first: session history, configuration, or integrations?

Sources and evidence

not affiliated with or endorsed by Moonshot AI and Kimi

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.