Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Run kimi import-sessions or enter /import-sessions to open the interactive page; the last 15 days is the default, with the last 30 days also available.
- Each run imports at most the 100 newest sessions in the selected window, and sessions imported before are skipped.
- Sessions without user prompts, subagent sessions, and non-interactive runs such as codex exec are not listed; missing project folders, sessions still being written, and Codex sessions forked or restarted from an earlier message are reported as skipped.
- Conversion runs locally, leaves the original session files unchanged, and does not call a model; that describes conversion only and does not establish that later work is offline, private, or free.
Choose the 15-day or 30-day window
The Kimi Code CLI 2.4.0 release notes dated October 28, 2026 introduced session import. Run kimi import-sessions from the command line or enter /import-sessions in the terminal interface (TUI) to open the same interactive import page. The default is the last 15 days; you can choose the last 30 days instead, then follow the progress and summary.
Start with the default window for recent work, or select 30 days when you need a wider recent range. The chosen window defines the candidate period; it does not guarantee that every session in that period will appear in the import results.
Account for the newest-100 limit per run
A run imports at most the 100 newest sessions in the selected window. Choosing 30 days therefore does not mean every record from those 30 days will be imported in one batch; older records may fall outside that run's limit.
Sessions imported before are skipped, so a skip on a later run is not by itself an import failure. The command reference does not promise pagination beyond the limit or a way to select one older session, so do not treat repeated runs as a guaranteed way to page through the complete history.
Separate unlisted records from reported skips
Some source records are not listed as candidates: sessions with no user prompt, subagent sessions, and non-interactive runs such as codex exec. These are different from items the import summary identifies as skipped.
Sessions imported before are skipped. Missing project folders, sessions still being written, and Codex sessions forked or restarted from an earlier message are also skipped and reported. First distinguish an unlisted record from one that was found and then skipped, then check the stated reason.
Find the imported session in its original project
An imported record becomes a regular Kimi Code session and returns to the project folder of the original session. Go to that project folder, run kimi, and enter /sessions to browse and resume the imported record.
The list marks the source as [Claude Code] or [Codex], while retaining the original title and last activity time. If you do not see a record, first confirm that you opened the matching project folder, then check whether the import summary reported a skip.
Understand what the imported message contains
An imported session starts with one message containing the converted conversation; tool calls and results become concise text notes. The conversion does not turn every historical event into a separate Kimi conversation message.
The first message includes as many recent turns as fit while leaving room to continue before context compaction. The complete history and a copy of the original session files are saved with the Kimi session for looking up earlier details.
Keep local conversion separate from later continuation
The default source locations are ~/.claude and ~/.codex. CLAUDE_CONFIG_DIR and CODEX_HOME can specify alternate Claude Code and Codex locations respectively. If an expected record is missing, check the source directory your tool actually uses, then compare the candidate list and import summary.
Conversion runs locally, does not modify the original session files, and makes no model call during conversion. Those facts describe only the conversion step: they do not establish that later continuation is offline, private, or free, and the cited material does not establish regional or plan pricing terms.
Sources
Frequently Asked Questions
Can importing a session restore project files to an earlier point?
The cited documentation describes conversation conversion and makes no promise of project-file rollback or restoration. Old tool results in a conversation also do not establish the current file state. Use the project’s existing version-control and backup process separately when you need an earlier code state.
Do Claude Code or Codex subscriptions and usage limits transfer with a session?
These sources define how sessions are read and converted; they do not establish any transfer of subscriptions, balances or service eligibility. A successful import is not evidence of model access or a quota reset. Confirm the account, model and fee conditions that apply when you continue working.