MoonshotAI / MoonshotAI/kimi-cli
session history lost on resume despite appearing on screen
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?
kimi, version 1.36.0
Which open platform/subscription were you using?
kimi code
Which model were you using?
kimi-for-coding
What platform is your computer?
windows 10
What issue are you seeing?
this is after i run /sessions and resume the session. the prior messages appear on the screen but the agent doesnt have it. I prompted it "do you see the previous messages? [previous message]" and it replied:
" The user is asking if I see previous messages. I should be honest that I don't see previous conversation history in this session, but I can look at the codebase to understand what w
as done."
What steps can reproduce the bug?
create session, fork it a few times, some undos, and then resume it
What is the expected behavior?
agent has messages
Additional information
this is pretty bad
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
Reproduce the issue in Kimi Code CLI on Windows 10 by creating a session, forking it several times, undoing some changes, and resuming it through /sessions. Compare the messages displayed after resume with the context available to the agent; done means the resumed agent can access the prior conversation history.
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