MoonshotAI / MoonshotAI/kimi-code
Feature Request: plugin management (/plugins) inside Kimi Code for VS Code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What feature would you like to see?
Since v0.6.0 the VS Code extension runs the same in-process Node engine as the CLI, but some CLI slash commands are not available in the extension. In particular, there is no way to manage plugins from the VS Code chat panel — typing the plugin-management command does nothing, and the only workaround is to switch to the terminal CLI and run /plugins there.
Could you either:
- Support plugin management (list / install / remove, equivalent to the CLI's /plugins) natively in the VS Code extension, or
- Document clearly which CLI slash commands are not available in the VS Code extension, so users know they must use the terminal CLI for those operations.
Environment: extension 0.6.3 (darwin-arm64) with CLI 0.27.0, VS Code / Cursor.
Additional information
Verified by checking the commands the extension registers in package.json (kimi.openInTab, kimi.focusInput, kimi.showLogs, etc.) — none of them is a plugin-management entry point. Searched existing issues for similar requests (#1399 is about a non-interactive CLI command, a different direction).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the extension commands registered in package.json and compare them with the CLI's /plugins behavior. Decide whether native list/install/remove support or documentation is the intended scope; done means the chosen path clearly handles plugin management or explains which commands require the terminal CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100