chore: archive kimi-cli and point users to Kimi Code CLI - #2659
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Update the CI dependency-pin gate and resolve the documentation consistency issues before approval.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
Archives Kimi CLI and redirects users to Kimi Code CLI, including a dependency-free kimi-code migration stub.
Changes:
- Adds archive notices and migration guidance across documentation and policies.
- Updates package metadata, lockfiles, release guidance, and changelogs.
- Adds tombstone behavior tests and removes the legacy dependency.
| File | Summary |
|---|---|
uv.lock |
Removes legacy dependency metadata |
tests/test_kimi_code_tombstone.py |
Tests tombstone behavior |
SECURITY.md |
Updates archived security policy |
sdks/kimi-sdk/README.md |
Adds archive notice |
README.md |
Adds archive notice and migration guidance |
pyproject.toml |
Marks package inactive and links replacement |
packages/kosong/README.md |
Adds archive notice |
packages/kimi-code/src/kimi_code/__init__.py |
Implements migration stub |
packages/kimi-code/pyproject.toml |
Updates tombstone package metadata |
packages/kaos/README.md |
Adds archive notice |
flake.nix |
Removes obsolete README override |
docs/zh/release-notes/changelog.md |
Adds archival release notes |
docs/zh/release-notes/breaking-changes.md |
Documents breaking changes |
docs/zh/guides/getting-started.md |
Adds archive callout |
docs/en/release-notes/changelog.md |
Adds archival release notes |
docs/en/release-notes/breaking-changes.md |
Documents breaking changes |
docs/en/guides/getting-started.md |
Adds archive callout |
docs/.vitepress/theme/EvolutionBanner.vue |
Updates archive banner |
CONTRIBUTING.md |
Redirects contributions |
CHANGELOG.md |
Adds archival release notes |
.agents/skills/release/SKILL.md |
Prevents dependency restoration |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
Devin Review found 1 potential issue.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4fc4f19f89
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 43604dce37
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| 2. Open a new terminal and run `kimi`. On first launch, it detects your Kimi CLI data in `~/.kimi/` and offers to migrate your config, MCP servers, input history, and sessions. You can also run `kimi migrate` at any time. Your original data in `~/.kimi/` is never modified or deleted. | ||
| 3. Run `/login` again, and re-authorize your MCP servers. Login credentials, MCP authorizations, and Kimi CLI plugins are not migrated. | ||
| 4. Uninstall the legacy CLI after migrating, e.g. `uv tool uninstall kimi-cli` or `brew uninstall kimi-cli`. |
There was a problem hiding this comment.
kimi shim
For users who originally installed kimi-cli with uv, this ordering removes the newly installed CLI: both uv and the migration installer manage ~/.local/bin/kimi (src/kimi_cli/ui/shell/update.py creates the replacement symlink there), while uv tool uninstall kimi-cli later deletes every executable recorded in the old tool receipt without checking whether the symlink target was replaced. I confirmed with uv 0.7.22 that uninstall logs Removing executable: .../kimi and deletes a substituted symlink. Move the legacy uninstall before installing Kimi Code CLI, or explicitly reinstall/relink the new CLI afterward; the same ordering should be corrected in the getting-started pages.
Useful? React with 👍 / 👎.
| # 开始使用 | ||
|
|
||
| ::: danger 警告 | ||
| **本项目已归档**。Kimi CLI 已停止维护，不再提供任何更新和安全修复，旧版将无法继续使用。请改为安装 [Kimi Code CLI](https://github.com/MoonshotAI/kimi-code)，详见 [迁移指南](https://moonshotai.github.io/kimi-code/zh/guides/migration)。 |
There was a problem hiding this comment.
After this page redirects readers to the replacement CLI, its feedback callout at line 24 still sends issues and suggestions to MoonshotAI/kimi-cli/issues. That conflicts with the newly updated README and CONTRIBUTING.md, which state that this repository is read-only and no longer accepts issues, so users of the newly installed CLI are directed to an unusable or wrong-product tracker. Update this callout in both locales to point to MoonshotAI/kimi-code.
AGENTS.md reference: docs/AGENTS.md:L20-L20
Useful? React with 👍 / 👎.
Description
Prepares the repository for archival. Kimi CLI (Python) is being discontinued in favor of Kimi Code CLI. Once the repo is archived, the README, docs site, security/contributing policies, and PyPI metadata can no longer be updated, so this PR lands those changes ahead of the final
1.51.0release.User-facing notices
<details>block.localStoragekey so users who dismissed the previous banner see it again. Add adangercallout to the EN/ZH getting-started pages.SECURITY.md/CONTRIBUTING.md: state that no further security updates or contributions are accepted, and point to Kimi Code CLI.kosong,pykaos,kimi-sdkREADMEs: add an archive notice.PyPI
kimi-cli: archived summary,Development Status :: 7 - Inactiveclassifier, and project URLs pointing to Kimi Code CLI.kimi-code(PyPI): this package was an alias ofkimi-cli, sopip install kimi-code/uv tool install kimi-codesilently installed the legacy CLI instead of the new Kimi Code CLI. It is now a dependency-free stub that prints install instructions for Kimi Code CLI and exits with status 1. Its README is now a standalone file instead of a symlink to the root README.Housekeeping
flake.nix: drop the override that replaced thekimi-codeREADME symlink, which is no longer needed now that the README is a real file.kimi-cliinpackages/kimi-code, so the upcoming bump does not reintroduce the dependency.sync-changelog.mjsalso adds the missing1.50.0heading; the ZH changelog gets the same heading.Testing
tests/test_kimi_code_tombstone.py: fails before the change, passes after.kimi-codewheel and installed it into a clean venv: onlykimi-codeis installed, and running it prints the notice and exits with status 1.make test: all suites pass except 7 failures intests/ui/test_usage.py, which fail identically onmain(pre-existing, unrelated).npm run build) passes.flake.nixchange was not verified locally (no Nix available).Follow-ups (not in this PR)
1.51.0(kimi-cli + kimi-code) via the usual bump PR.