MoonshotAI / MoonshotAI/kimi-cli
偶现 Http 400 Error || Occasionally Http 400 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?
1.37
Which open platform/subscription were you using?
Which model were you using?
kimi-for-coding
What platform is your computer?
Windows11 x64
What issue are you seeing?
报错:
Error code: 400 - {'error': {'message': 'invalid request: unknown think_v2 option: keep_reasoning_content', 'type': 'invalid_request_error'}}
What steps can reproduce the bug?
随机出现。尚不清楚是服务器问题还是实现传参问题。
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
1.37
Which open platform/subscription were you using?
Which model were you using?
kimi-for-coding
What platform is your computer?
Windows 11 x64
What issue are you seeing?
Error:
Error code: 400 - {'error': {'message': 'invalid request: unknown think_v2 option: keep_reasoning_content', 'type': 'invalid_request_error'}}
What steps can reproduce the bug?
Appear randomly. It's unclear whether it's a server problem or a parameter-passing problem.
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 the intermittent error with Kimi Code CLI 1.37 on Windows 11, then trace the Python CLI request handling for the think_v2 and keep_reasoning_content parameters. Compare the failing and successful requests to determine whether the 400 response comes from parameter construction or the service, and verify the identified cause with a repeatable test.
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
- 35/100