MoonshotAI / MoonshotAI/kimi-cli
/plugins crashes with TypeError when 2+ plugins are installed (v0.29.0, Windows)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
Summary
The /plugins management screen crashes the whole CLI with TypeError: Cannot read properties of undefined (reading 'value') whenever two or more plugins are installed. With zero or one installed plugin the screen opens fine.
Environment
- kimi-code 0.29.0 (single-file binary, Node v24.15.0)
- Windows x64,
uiMode=shell - Installed plugins:
kimi-datasource(official, zip-url),superpowers(github.com/obra/superpowers),vercel-plugin(github.com/vercel/vercel-plugin)
Steps to reproduce
- Install any two plugins (e.g. the official
kimi-datasourceplus any GitHub plugin). - Start
kimi. - Type
/pluginsand press Enter. - The TUI exits immediately; the session is lost.
Log (~/.kimi-code/logs/kimi-code.log):
ERROR uncaughtException, restoring terminal and exiting
error="TypeError: Cannot read properties of undefined (reading 'value')"
Bisect results (reproduced headlessly via ConPTY automation)
| Installed plugins | /plugins |
|---|---|
| 0 | ✅ opens |
| any single one (each of the 3 tested separately) | ✅ opens |
| any pair (all 3 combinations tested) | ❌ crashes |
| all 3 | ❌ crashes |
So the trigger is plugin count ≥ 2, not any specific plugin, manifest, or source type.
Additional notes
kimi doctorreports all config files valid.- The installed plugins themselves work fine in sessions (their MCP servers connect and tools are available) — only the
/pluginsscreen is affected. - Suspected location: building the select/option list for the Installed tab when there are ≥2 entries (
.valueread on an undefined option).
Expected behavior
/plugins opens the management UI regardless of how many plugins are installed.
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 at the /plugins management screen and inspect how the Installed tab builds its select/option list when multiple plugins are present. Reproduce with two installed plugins using the headless ConPTY setup, then verify that /plugins opens without the TypeError and that the zero-, one-, and multiple-plugin cases remain functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100