K3Nova
Check how Kimi is installed
Run these before uninstalling so you remove the right package.
command -v kimi
kimi --version
npm list -g --depth=0 | grep -i kimi
pnpm list -g --depth=0 | grep -i kimi
yarn global list | grep -i kimiKeep what matters before you remove anything
Uninstall Kimi Code with the same channel that installed it. Then decide whether to keep or clear sessions, config, credentials, plugins, and logs. Those are separate choices.
For a normal uninstall, remove the app or global command and leave the data root alone. For a clean reset, export important sessions first and then clear the documented data folders.
Copyable commands
Uninstall the binary first, then decide whether to preserve, move, or clear local data.
Save the current session
Export before removing the command if you may need the latest context later.
mkdir -p "$HOME/kimi-code-backup"
kimi export -y -o "$HOME/kimi-code-backup/latest-session.zip"Remove the installed command
Choose the one package-manager line that matches the install source.
npm uninstall -g <package-name>
pnpm remove -g <package-name>
yarn global remove <package-name>Verify PATH after uninstall
Open a new terminal or refresh the shell hash before checking again.
hash -r
command -v kimi || echo "kimi is not on PATH"AI handoff prompt and permissions
Copy this prompt into Kimi Code, K3Nova, or another AI agent. Keep approval manual for file writes, shell commands, account actions, and secrets.
Copyable AI prompt
Use this to give the agent the task and safety boundary in one message.
You are my AI agent for this task: remove Kimi Code from the original install channel, verify PATH cleanup, and keep data-root deletion separate from package removal.
Start by restating the goal and the permissions you need.
Use official docs or the files I provide before making claims.
Give me a direct answer first, then a short table or checklist.
If commands are needed, show exact copyable commands without a shell prompt.
Ask before writing files, running shell commands, deleting or moving data, logging in, spending money, changing account settings, or handling API keys.
Stop and ask me when a step requires secrets, payment, account access, destructive cleanup, or a permission broader than the task.Recommended AI permissions
| Permission | Give AI | Why |
|---|---|---|
| Inspection | Allow Read, Grep, Glob, and package-list commands. | The agent needs to find how Kimi Code was installed. |
| Backups | Ask before creating or moving backups. | Backup location and size should be visible. |
| Uninstall or move | Ask before npm, pnpm, yarn, mv, rm, rmdir, or credential cleanup. | Removal can be hard to undo. |
| Credentials | Deny reading or printing OAuth files, API keys, and MCP credentials. | The agent can describe paths without exposing secrets. |
Uninstall paths
| Install type | Removal path | Afterward |
|---|---|---|
| Global npm package | npm uninstall -g the package name you installed | Check that kimi is no longer on PATH |
| pnpm or yarn global install | Use the same global package manager | Open a new terminal before testing PATH |
| IDE extension | Remove from the editor extension manager | Restart the editor |
| Local data reset | Clear selected folders under KIMI_CODE_HOME | Export sessions first |
Safe cleanup order
Remove the install
Use npm, pnpm, yarn, a native package, or your IDE extension manager depending on the original install path.
Clear plugins only if needed
Disable or remove plugins when plugin behavior is the reason for uninstalling.
Clear credentials carefully
Use logout where available, then remove only the matching provider or MCP credential files if a deeper cleanup is required.
Verify the command is gone
Open a new terminal and run which kimi or kimi --version. If it still responds, another install path remains.
What can remain after uninstall
Package uninstall
Global package removal usually removes the command but leaves user data behind.
IDE uninstall
The VS Code extension is separate from the CLI executable and should be removed from the editor extension manager.
Clean reinstall
After uninstalling, move the data root aside instead of deleting it immediately. That gives you a rollback if you later need an old session.
FAQ
Why does kimi still run after uninstall?
Another install path may still be on PATH, or the terminal needs to be restarted.
Can I reinstall without losing old sessions?
Yes. Package reinstall can keep existing data unless you clear the data root.
Should I delete credentials manually?
Only if logout or package removal does not meet your cleanup goal, and only for the matching provider or MCP account.