K3Nova
Confirm Kimi Code and open a session
Start with the installed CLI and validate config before changing plugin state.
kimi --version
kimi doctor
kimiGoal and short answer
Use Kimi Code plugins when you want reusable CLI capabilities, team workflows, Agent Skills, or MCP-backed tools to travel with your coding environment. The official plugin manager is the right place to install, enable, disable, inspect, and remove them.
The fastest safe path is to open the plugin manager, check the publisher and trust badge, install only what you understand, then reload or start a new session so the current Kimi Code process sees the change.
Copyable commands
Run the shell checks in a terminal. Paste slash commands inside the Kimi Code TUI.
Inspect plugins inside the TUI
Use these after the Kimi Code terminal UI opens.
/plugins
/plugins list
/plugins marketplace
/plugins info <plugin-id>Install, reload, and toggle a plugin
Install only from a path or URL you trust, then reload before testing.
/plugins install <path-or-url>
/plugins reload
/plugins enable <plugin-id>
/plugins disable <plugin-id>Remove a plugin after a failed test
Remove the plugin record, reload manifests, and repeat the same small prompt.
/plugins remove <plugin-id>
/plugins reloadAI 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: audit my current Kimi Code plugin setup, choose whether to install, disable, reload, or remove a plugin, and keep the change reversible.
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 |
|---|---|---|
| Read-only project access | Allow Read, Grep, and Glob only in the selected project or config folder. | Lets the agent inspect state before acting. |
| Shell commands | Ask before Bash or any CLI command; run one command at a time. | Commands can change files, packages, sessions, or network state. |
| File edits | Ask before Write or Edit, and require a diff before applying changes. | Prevents hidden config or source edits. |
| Hard stops | Deny payment, login, secret exposure, account changes, and destructive delete commands. | These are not safe to automate casually. |
Runbook
Open the plugin manager
In the Kimi Code TUI, run /plugins. Use the Installed, Official, Third-party, and Custom tabs to see what is already enabled and what can be added.
Install with a source you trust
Official marketplace plugins are the lowest-friction path. For custom or third-party sources, read the manifest and publisher details before accepting the confirmation prompt.
Reload after changes
After installing, disabling, or removing a plugin, run /reload or start a new session. The running session does not always pick up changed plugin capability immediately.
Remove before debugging deeply
If a new tool call starts failing after a plugin change, disable or remove that plugin first, reload, and repeat the same small prompt before changing your model or account settings.
Plugin actions
| Need | Use | Check |
|---|---|---|
| Install a marketplace plugin | /plugins, then Official or Third-party | Publisher, trust badge, permissions, reload |
| Install a custom plugin | /plugins install with a local path, zip, or GitHub URL | Manifest name, source URL, and why the plugin is needed |
| Temporarily stop a plugin | Disable it from Installed | Repeat the same prompt after reload |
| Clean up a plugin | Remove it from Installed | Managed files and original source may remain; check data locations if you need a deeper cleanup |
Notes before you continue
What plugins can add
A plugin can package Skills, commands, MCP servers, and reusable workflows. That is useful for finance checks, browser helpers, repository routines, or team-specific review steps.
What plugins should not do
Do not install a plugin just because it promises broad capability. If it can call external services or run tools, it should have a clear job and a publisher you trust.
Where plugin data lives
Installed plugin records and managed copies live under the Kimi Code data directory, so cleaning or relocating KIMI_CODE_HOME changes which plugins are visible.
FAQ
Do Kimi Code plugins update the current session immediately?
Usually you should reload or start a new session after changing plugin state.
Can a plugin add MCP tools?
Yes, plugin manifests can declare MCP servers, which can be enabled or disabled from the plugin manager.
Should I install custom plugins from random URLs?
No. Read the source, publisher, and manifest first, then install only when the job and trust boundary are clear.