MoonshotAI / MoonshotAI/kimi-cli
[Bug] Windows: kimi.exe v1.41.0 has blank FileVersionInfo, causing VS Code extension to reject it as "incompatible"
Open
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?
version 1.41.0
Which open platform/subscription were you using?
/login
Which model were you using?
kimi-for-coding
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
All FileVersionInfo fields are empty, causing extension compatibility check to fail.
What steps can reproduce the bug?
- Install kimi-cli on Windows via official install script
- Check FileVersionInfo with Get-Command kimi | Format-List
- VS Code extension rejects the CLI due to missing version metadata
What is the expected behavior?
Windows executable should have proper version info embedded
Additional information
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 Windows install from the official install script, then inspect kimi.exe with PowerShell using Get-Command kimi | Format-List. Trace the Windows packaging or release configuration that produces version metadata; done means the executable exposes populated FileVersionInfo fields and the VS Code extension accepts version 1.41.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100