Subject: Context compaction bug — Kimi Code reopens an already completed and deleted task

What version of Kimi Code CLI is running?

v0.6.3

Which open platform/subscription were you using?

login

Which model were you using?

K2.7 coding

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Kimi Code 07192026.pdf

Subject: Context compaction bug — Kimi Code reopens an already completed and deleted task

After completing the task, documenting it, deleting estado.md, and explicitly reporting “He completado los pendientes técnicos del estado.md y eliminado el archivo”, Kimi Code later hits “Context compacted” and incorrectly reactivates the original instruction. It says the user is asking to read estado.md again and calls ReadFile estado.md, even though that file had already been deleted and the task had been reported as completed.

Expected: completed tasks remain closed after compaction; old fulfilled instructions must not be reactivated; missing deleted files should trigger verification or a question, not reopening the task.

Actual: after context compaction, the original instruction becomes active again and the agent attempts to read the deleted estado.md.

Evidence: attached transcript, pages 1, 37–39, and 95.

What steps can reproduce the bug?

Steps to reproduce:

1. Start a Kimi Code CLI session in a project with an estado.md file containing pending tasks.
2. Ask Kimi Code to: read estado.md, continue with the pending tasks, document the changes, and then delete estado.md. Allow it to use subagents/AgentSwarm.
3. Let Kimi Code complete the task. In my session it reported the pending items as completed, documented the changes, deleted estado.md, and explicitly said: “He completado los pendientes técnicos del estado.md y eliminado el archivo.”
4. Continue the same session with other unrelated tasks until the context is compacted. In the attached transcript this happens at the “Context compacted” marker.
5. Immediately after compaction, Kimi Code reactivates the original instruction as if it were still pending: “El usuario me pide que lea estado.md, continúe con los pendientes, documente y elimine estado.md...” and calls ReadFile estado.md, even though estado.md was already deleted and the task had been reported as completed.

Expected result:
After a task is completed and its state file is deleted, context compaction must preserve that the task is closed. Kimi Code should not reopen the original instruction or try to read the deleted estado.md again. If the file is missing, it should verify or ask instead of assuming the old task is still active.

Actual result:
After “Context compacted”, Kimi Code treats the original fulfilled instruction as active again and attempts to read estado.md.

Additional context:

• This is a conversational/session-state bug; I do not have a standalone code snippet that reproduces it outside the session.
• Attached transcript: Kimi Code 07192026.pdf
• Key pages: page 1 original instruction; pages 37–39 completion, documentation, and deletion of estado.md; page 95 “Context compacted” and the old task being reopened; page 96 confirms estado.md no longer exists.
• Context usage before/after compaction: n/a

What is the expected behavior?

No response

Additional information

No response

Start by reviewing the context-compaction and session-state handling in the Kimi Code CLI, using the attached transcript pages 37–39 and 95–96 as behavioral evidence. Reproduce the session with estado.md, task completion, deletion, and later compaction. Done means completed instructions stay closed after compaction and the deleted file is not reopened without verification or a question.