MoonshotAI / MoonshotAI/kimi-cli

Model performance degredation in recent update

Open
#1,548 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.24.0

Which open platform/subscription were you using?

kimi-code

Which model were you using?

kimi-for-coding

What platform is your computer?

macOS

What issue are you seeing?

Performance drop since recent update. I have a effect-ts monorepo which the model was quite good at navigating and following AGENTS.md instructions, but somehow in recent useage I noticed a lot of mistakes, not following rules, over complicating code, confusion and overall lower satisfcation using the tool as it makes too many mistakes.

What steps can reproduce the bug?

Hard to say, my project configs are setup for my rules but it's just a general observation. Heres what the LLM outputted based on my feedback.

Performance Degradation Report

Task: Fix circular dependency in TypeScript Effect-TS monorepo
Failure Mode: Multiple cascading errors, rule violations, poor code quality

Specific Failures:

  1. Critical Rule Violation - Used git checkout -- . despite AGENTS.md explicitly forbidding it. Bypassed all
    ety checks (untracked file check, stash, explicit approval).
  2. Inconsistent Code Quality - Created files with:
    • Wrong imports (.js extensions forbidden by AGENTS.md)
    • Wrong patterns (Effect.Tag instead of Context.Tag as used in codebase)
    • Unnecessary complexity (placeholder Default layers, re-exports user explicitly forbade)
  3. Incomplete Solution - Failed to fully break the circular dependency. Moved ApiClientService but left 40+ f
    s still importing from @ma/provider.
  4. Lack of Care - User had to repeatedly correct the same mistakes. Failed to verify work at each step.
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

No repository file, test, or reproducible steps are named. Start by reviewing the reported Kimi Code CLI version 1.24.0, model kimi-for-coding, and macOS environment, then compare behavior against the preceding update using a representative effect-ts monorepo with its AGENTS.md instructions. Done requires a reproducible performance or behavior regression with an objective comparison.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, python, typescript
Domain
ai, cli, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.