Kimi Code imports past sessions: bring context back to the original project

On October 28, 2026, Kimi Code CLI released version 2.4.0, adding imports from Claude Code and Codex. Users can choose history from the past 15 or 30 days and continue it as ordinary Kimi Code sessions.

The import does more than copy a summary and discard everything else. Sessions keep their titles, last activity times and source labels. Complete history and copies of the original session files are also saved with the imported session. Session import guide

Suppose you analyzed a project issue in another coding tool last week and want to continue in Kimi Code today. The conversation history can preserve the causes and approaches already discussed, without relying on memory to explain them again.

The first message in the imported session contains recent conversation turns, with tool calls and results converted into brief text records. Earlier details remain available in the saved full history. Conversion itself runs locally, does not call a model and does not modify the original session files. This applies to the import conversion; it does not establish that later model conversations are entirely offline. What is preserved and converted

Before continuing, check the current project files against the old discussion. Reading a historical command does not mean it has run again in the current environment.

Use Kimi Code CLI 2.4.0 or later, with the original tool's sessions and project directories still on your computer. The default locations are ~/.claude and ~/.codex; custom locations use CLAUDE_CONFIG_DIR and CODEX_HOME, respectively. Storage locations

1. Run kimi import-sessions in a terminal, or enter /import-sessions in Kimi's terminal interface. Choose the last 15 days (the default) or 30 days, then review progress and the summary.
2. Check why sessions were skipped. Each run imports at most the latest 100 sessions; previously imported sessions are not added again. Sessions without a user prompt, subagent sessions and non-interactive records such as codex exec are not listed. Sessions still being written, sessions whose project directory no longer exists, and Codex sessions that were forked or restarted from an earlier message are skipped. Limits and exclusions
3. Return to the original project directory, run kimi, and enter /sessions. Find and open the session labeled [Claude Code] or [Codex]. Find an imported session
4. Begin with a bounded request, for example: “Summarize the causes we previously found, compare them with the current files, and list what still needs checking. Do not edit code yet.” This is a suggested prompt. Review the result before choosing the next action.