MoonshotAI / MoonshotAI/kimi-code

Impossible to resume crashed sessions

Open
#660 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What version of Kimi Code is running?

0.14.0

Which open platform/subscription were you using?

Kimi Code

Which model were you using?

kimi-k2.6

What platform is your computer?

Linux

What issue are you seeing?

When session is killed midflight by OOM or other events, it usually becomes impossible to resume. It loads but in case there in an incomplete tool call it will get stuck on error similar to this
Error: [provider.api_error] 400 an assistant message with 'tool_calls' must be followed by tool messages responding to each 'tool_call_id'. The following tool_call_ids did not have response messages: Agent:122
If this persists, run /export-debug-zip and share the file with us for diagnosis. Please don't share it publicly.

What steps can reproduce the bug?

start kimi, let it execute something with tool calls, forcefully kill it when it's calling a tool, load the session again and try to write a message

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 the crash during a tool call in the Kimi Code CLI, then trace the session loading and resume path for incomplete tool calls. Done means a session forcibly interrupted mid-tool-call can be loaded and accept a new message without the provider tool-message error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.