MoonshotAI / MoonshotAI/kimi-code

VSCode中MCP报错 'gbk' codec can't encode character

Open
#1,211 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What version of Kimi Code is running?

VSCode 插件版本 0.5.10

Which open platform/subscription were you using?

nm926635@gmail.com

Which model were you using?

kimi-for-coding

What platform is your computer?

win10

What issue are you seeing?

MCP不可用,提示 \u2717 Connection failed: UnicodeEncodeError: 'gbk' codec can't encode character '\u2713' in position 0: illegal multibyte sequence,设置环境变量PYTHONIOENCODING=utf-8无效,之前是可用的

context7报错
Context7 Documentation MCP Server v3.2.2 running on stdio
\u2717 Connection failed: UnicodeEncodeError: 'gbk' codec can't encode character '\u2713' in position 0: illegal multibyte sequence

playwright报错
\u2717 Connection failed: UnicodeEncodeError: 'gbk' codec can't encode character '\u2713' in position 0: illegal multibyte sequence

Image
What steps can reproduce the bug?

1、打开vscode
2、找到MCP
3、安装context7或者playwright
4、配置环境变量PYTHONIOENCODING=utf-8
5、测试MCP

What is the expected behavior?

No response

Additional information

No response

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 MCP connection failure from the VSCode plugin on Windows 10 with either Context7 or Playwright, using the reported PYTHONIOENCODING setting. Trace the MCP connection entry point around the UnicodeEncodeError; done means both reported MCP servers connect without the GBK encoding failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.