MoonshotAI / MoonshotAI/kimi-cli

【bug] API Error: 400 {"error":{"type":"invalid_request_error","message":"Invalid request Error"},"type":"error"}

Open
#778 18 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?

Version: 2.1.23

Which open platform/subscription were you using?

win11 , powershell

Which model were you using?

Model: Default (claude-sonnet-4-5-20250929)

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?
Image
What steps can reproduce the bug?

仔细阅读 "E:\问kimi-4个文件\Task.md",结合文件内容,深度思考,规划实施方案,然后和我确认。

● Read 1 file (ctrl+o to expand)

● 我已经阅读了任务文件。这是一个深度个人健康数据分析项目,需要综合四个维度的数据进行跨学科分析。让我先探索数据文件的目录结构,了解具体的文件格式和
容。

● Searched for 2 patterns, read 1 file (ctrl+o to expand)

● 找到了数据文件。让我读取这些文件以了解数据格式。

● Read 4 files (ctrl+o to expand)
⎿  API Error: 400 {"error":{"type":"invalid_request_error","message":"Invalid request Error"},"type":"error"}

✻ Churned for 1m 10s

❯ continue
⎿  API Error: 400 {"error":{"type":"invalid_request_error","message":"Invalid request Error"},"type":"error"}

2026.1.27 13点之前重试了两次同样的情况,17点第三次尝试暂时没有发现问题。

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 report with Kimi Code CLI 2.1.23 on Windows 11 and PowerShell, using the default model and the file-reading sequence described in Task.md. No repository file or test is named, so trace the CLI entry point that handles the 400 response and compare successful and failing requests. Done means identifying the cause and demonstrating the fix with a regression test or reliable reproduction.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.