Kimi Code CLI · Migrating from kimi-cli

The new Node.js-based Kimi Code CLI offers simpler installation, faster startup, and a redesigned terminal. The legacy kimi-cli will gradually be retired.

Install the new version

Follow Getting started, then migrate your existing data.

Migrate settings and sessions

On first launch, kimi checks ~/.kimi/ for legacy data. Choose to migrate now, postpone, or dismiss future prompts.

To start migration manually:

Bash

Config only imports settings without chat history.
Config + N sessions also imports selected conversations.

Review the completion summary. Imported sessions carry an [imported] label.

What is transferred?

Migration includes config.toml, MCP server settings, input history, and selected conversations.

OAuth credentials, MCP authorizations, and legacy plugins are excluded. Run /login again, reauthorize MCP servers, and configure plugins as needed.

Your original ~/.kimi/ data stays untouched. The legacy application remains usable. Repeating migration does not duplicate previously imported sessions.

See the migration guide maintained by the Kimi Code team.

Was this article helpful?