MoonshotAI / MoonshotAI/kimi-cli

Random KIMI CLI crash on WSL

Open
#2,163 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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?

kimi, version 1.41.0

Which open platform/subscription were you using?

API KEY

Which model were you using?

KIMI 2.6

What platform is your computer?

Windows 11 with WSL running Ubuntu / 22 to 26 tested on all images

What issue are you seeing?

Random crash without explanation. I invested 2 days before writing this.

  1. Did windows reset
  2. Tested on all Ubuntu WSL version from 22 to 26
  3. Upgraded to WSL 2 dev version from stable
  4. Changed available cores ram network swap size etc. WSL settings
  5. Test with pythion 3.12 and 3.13
  6. Teste on Windows Termina, Visual Studio Developer Console, WSL Ubuntu console
  7. Did bios reset

Still I get random failures of kimi. usuall chating was fine file access operations were leading to the random crashes. Sometimes instant sometimes after 2 minutes of generation where I had to just Approve the file creation. I noted that on file save a yellow form is loading with the confirmation options. Usually crashes appear there. I checked also file permission is same as current user not root.

NOTE - Same on windows directly installed KIMI CLI executed via powershell on Windows. My WSL environment work fine with nanobot and kimi-2.6 as model.

What steps can reproduce the bug?

Work with multiple files at once in my case 3. was enough ~50KB md files. Asked for summary and merge

What is the expected behavior?

CLI works stable across the session.

Additional information

Log was clear nothing there. Attaching for reference.

kimi.log

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached kimi.log, then reproduce the crash with Kimi CLI 1.41.0 on Windows 11 with WSL Ubuntu while summarizing and merging three roughly 50KB Markdown files. Compare file-save approval behavior across WSL and native PowerShell; done means the CLI completes the session without random crashes and the logs identify no unexplained failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, ubuntu
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.