MoonshotAI / MoonshotAI/kimi-cli
Windows 11 企业版上使用uv安装的kimi cli启动太慢 || The kimi cli installed using uv on Windows 11 Enterprise Edition starts too slowly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
What version of Kimi Code CLI is running?
1.39.0
Which open platform/subscription were you using?
/login
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
在windows 11 企业版上kimi cli启动速度太慢，每次启动甚至得要至少1分钟。经过AI对日志的排查，发现是因为ReadMediaFile 和 FetchUrl 这两个工具需要在启动的时候加载，但在启动的时候这两个工具加载速度太慢导致。此问题需要尽快处理
What steps can reproduce the bug?
- 在某个目录下启动powershell
- 输入 kimi 或 kimi --continue
- 就一直等吧
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
1.39.0
Which open platform/subscription were you using?
/login
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
On Windows 11 Enterprise Edition, the startup speed of kimi cli is too slow, and it takes at least 1 minute to start each time. After AI checked the logs, it was found that the two tools ReadMediaFile and FetchUrl need to be loaded at startup, but the loading speed of these two tools is too slow at startup. This issue needs to be addressed as soon as possible
What steps can reproduce the bug?
- Start powershell in a certain directory
- Enter kimi or kimi --continue
- Just keep waiting.
What is the expected behavior?
No response
Additional information
No response
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
Reproduce the delay by running kimi and kimi --continue from PowerShell on Windows 11, then inspect startup logs around loading ReadMediaFile and FetchUrl. Trace which startup step causes the wait and measure the launch time before and after the change; done means the CLI starts without the reported minute-long delay and both tools remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, python
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100