Kimi Code 1.2.0: see whether a follow-up reaches the current task

Kimi Code released desktop version 1.2.0 on October 28, 2026. It adds unread, read and insertion-progress indicators for messages that steer a task while it is running. Official changelog

Kimi Code is an AI coding tool that can read project materials, execute tasks and change files. After a task begins, you may realize you need to add a constraint. The new indicators help show whether that follow-up enters the current turn, rather than leaving you to infer this from a chat bubble appearing.

Suppose you ask the AI to change an event registration page, then remember: “Only change the button text; keep the existing layout for now.” Sending a whole new task may repeat the original requirements, while saying nothing may let the work continue in the wrong direction.

The input and context guide explains that you can add scope, constraints or clarification during execution. Message indicators help confirm whether that addition enters the current turn. In this example, watch the message first, then check the button and layout in the result.

“Read” or “inserted” describes message handling, not a page already changed correctly. If the follow-up conflicts with changes already made, you still need to inspect the actual differences and explain how to adjust them. The official documentation does not promise that inserting a message automatically undoes previous actions.

Use Kimi Code desktop 1.2.0 or later and open the project session you are working in. The registration-page scenario below is a suggested use.

1. While the task is running, add: “Only change the registration button text. Keep the layout, and explain what changed when you finish.” Be specific about the change instead of saying “Do it like before.”
2. Watch the message's unread, read and insertion indicators. New input may first enter a queue. To move the current input to the front, the documented shortcut is Command + S on macOS or Ctrl + S on Windows. Adding input during a run
3. When a result appears, open the changed files or preview the page. Check the button text and layout, then run the project's existing validation commands as appropriate. Message status shows whether communication occurred; files and pages show whether the result meets the requirement. Execution and review

If you want to stop a background task, find and stop it in the work bar above the composer. Sending “stop for a moment” is still a follow-up input; it is not a receipt confirming that the background task has stopped.