MoonshotAI / MoonshotAI/kimi-cli

[Bug] Windows 中文系统:1.38.0+ 版本内置 skill 文件编码错误 || [Bug] Windows Chinese system: 1.38.0+ version built-in skill file encoding error

Open
#2,070 2 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?

版本信息:昨天 1.38.0 正常,今天升级1.39后报错

Which open platform/subscription were you using?

/login

Which model were you using?

kimi-k2.6

What platform is your computer?

x64

What issue are you seeing?

错误信息: 'utf-8' codec can't decode byte 0xcf in position 46
系统环境:Windows, utf-8编码

What steps can reproduce the bug?

启动不了

What is the expected behavior?

No response

Additional information

session-c2a41388-903c-4a8a-b378-a4f9e00d1a00.zip 附上report


What version of Kimi Code CLI is running?

Version information: 1.38.0 was normal yesterday, but an error occurred after upgrading to 1.39 today.

Which open platform/subscription were you using?

/login

Which model were you using?

kimi-k2.6

What platform is your computer?

x64

What issue are you seeing?

Error message: 'utf-8' codec can't decode byte 0xcf in position 46
System environment: Windows, utf-8 encoding

What steps can reproduce the bug?

Can't start

What is the expected behavior?

No response

Additional information

session-c2a41388-903c-4a8a-b378-a4f9e00d1a00.zip Attached is report

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 reproducing the startup failure on Windows with a Chinese system setting, using the reported upgrade from 1.38.0 to 1.39 and the UTF-8 decode error. Trace the Kimi Code CLI startup path that loads its built-in skill files and identify the file or encoding boundary involved. Done means the CLI starts successfully on the reported environment without the decoding 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
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.