MoonshotAI / MoonshotAI/kimi-cli

Error: [compaction.failed] APIStatusError: 400 The request was rejected because it was considered high risk

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

0.6.0

Which open platform/subscription were you using?

/login

Which model were you using?

Kimi-k2.6

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

● Compaction cancelled
Error: [compaction.failed] APIStatusError: 400 The request was rejected because it was considered high

What steps can reproduce the bug?

● Compaction cancelled
Error: [compaction.failed] APIStatusError: 400 The request was rejected because it was considered high risk

session_f5bd9a80-3176-447d-91c8-b48e60efccfc.zip

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 compaction cancellation on Kimi Code CLI 0.6.0 on Windows with the Kimi-k2.6 model, then inspect the attached session archive and the compaction error path. The issue names no source files or tests and does not state expected behavior; done should be defined after confirming whether the high-risk API rejection is handled or reproduced with a clear outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, cli
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.