MoonshotAI / MoonshotAI/kimi-cli
`kimi term` crashes on Windows due to missing `fcntl` module, followed by secondary `rich.pretty` rendering error
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?
kimi, version 1.41.0
Which open platform/subscription were you using?
kimi code
Which model were you using?
k2.6
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Bug Report: kimi term crashes on Windows due to missing fcntl module, followed by secondary rich.pretty rendering error
Environment
- OS: Windows 10/11 (x64)
- Python version: 3.14.0 (via
pythoncore-3.14-64) - Installation method:
uv tool install kimi-cli - Package path:
C:\Users\JackyYe\AppData\Roaming\uv\tools\kimi-cli\Lib\site-packages\toad
Reproduction Steps
- Install
kimi-clion Windows:uv tool install kimi-cli - Run:
kimi term(orkimi acp, which internally triggers the same terminal app) - Application crashes immediately before the TUI renders
Expected Behavior
The terminal UI (kimi term) should launch successfully, or at least fail gracefully with a clear error message.
Actual Behavior
The application crashes with a cascading exception:
Primary Error (Root Cause):
What steps can reproduce the bug?
Run: kimi term
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
Start by reproducing kimi term and kimi acp on Windows with Python 3.14, then trace the terminal application's startup path in the installed toad package. Identify where the missing fcntl import and subsequent rich.pretty rendering error occur; done means the TUI launches or reports a clear, non-cascading error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100