MoonshotAI / MoonshotAI/kimi-cli
Latest versions are far slower
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.46.0
Which open platform/subscription were you using?
Kimi Code
Which model were you using?
Kimi-k2.6
What platform is your computer?
Linux 7.0.10-mnt-reform-arm64 aarch64 unknown
What issue are you seeing?
Previously Kimi was quite fast for a low-specced machine like the MNT Pocket Reform. Unfortunately, the newer version have gotten drastically slower. Part of the reason I chose Kimi is the CLI was faster with lower overhead than Claude.
What steps can reproduce the bug?
Run Kimi-cli on a lower-specced machine
What is the expected behavior?
Kimi should go fast.
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
The report names no file, test, or entry point. Start by reproducing Kimi Code CLI 1.46.0 on a low-spec Linux aarch64 machine, then compare its speed with an earlier version to identify whether the regression is measurable and where it occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- cli, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100