MoonshotAI / MoonshotAI/kimi-cli

System prompt conflicting with my desired workflow

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

Kimi Code v0.12.0

Which open platform/subscription were you using?

the api key one

Which model were you using?

k2.7-coding

What platform is your computer?

debian

What issue are you seeing?

I have strict guidelines (mentioned in multiple places) about not modifying existing tests unless that's the task (ie. when implementing features or changes, create new tests, don't modify existing ones).

The agent included a "modify existing tests" step in a runfile, and when I quizzed it, it said:

● Yes, you're right. The kimi-code harness system prompt does contain a testing guideline
in the "General Guidelines for Coding" section, roughly:

│ "If user mentioned any failed tests, you should make sure they pass after the
│ changes."


It would be good if there were no guidelines like this in the system prompt which got in the way of the agent behaving the way I want it to.

What steps can reproduce the bug?

Try to stop the agent from ever modifying existing tests when implementing new features and bug fixes

What is the expected behavior?

Follow my instructions

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 file or test is named. Start by locating the Kimi Code harness system prompt and its “General Guidelines for Coding” section, then reproduce the conflict with the stated test-modification instruction. Done means the agent follows the user's instruction without the system prompt overriding it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.