MoonshotAI / MoonshotAI/kimi-cli
kimi code vscode 插件很耗内存 || kimi code vscode plug-in consumes a lot of memory
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?
0.4.5
Which open platform/subscription were you using?
vscode
Which model were you using?
No response
What platform is your computer?
Darwin 23.6.0 arm64 arm
What issue are you seeing?
我使用vsocde 安装kimi code 插件, 在长时间执行一个任务,大概context 占用57%,左右的时候 vscode 占用的20g 内存。 我总共打开了两个vscode 窗口, 当我把kimi code 正在运行的vscode 窗口关闭之后,vscode 占用8g 内存。
并且在关闭vscode 的时候,提示卡顿。
What steps can reproduce the bug?
在vscode 安装kimi code
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
0.4.5
Which open platform/subscription were you using?
vscode
Which model were you using?
No response
What platform is your computer?
Darwin 23.6.0 arm64 arm
What issue are you seeing?
I used vsocde to install the kimi code plug-in. When executing a task for a long time, the context occupied about 57%, and vscode occupied about 20g of memory. I opened a total of two vscode windows. When I closed the vscode window where kimi code was running, vscode occupied 8g of memory.
And when closing vscode, it prompts for lag.
What steps can reproduce the bug?
Install kimi code in vscode
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
No source file, test, or entry point is identified in the report. Reproduce the issue with Kimi Code CLI 0.4.5 in VS Code on Darwin 23.6.0 arm64 during a long-running task, measure memory growth and shutdown behavior, and use those observations to define the fix and its verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vscode
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100