MoonshotAI / MoonshotAI/kimi-cli
Edit tool keeps failing in new kimi-code
Open
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?
/login
Which model were you using?
k2.6
What platform is your computer?
debian
What issue are you seeing?
I'm seeing this error pretty frequently in the output since the update to kimi-code:
old_string not found in sm-server, the file contents may be out of date. Please use
the Read Tool to reload the content.
What steps can reproduce the bug?
Use the product
What is the expected behavior?
Not seeing that erro
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 failure in Kimi Code v0.12.0 on Debian with the reported /login and k2.6 setup, focusing on the Edit Tool and its Read Tool reload path. Trace where the “old_string not found” message is emitted; done means the reported editing workflow no longer produces this error unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100