What happened | Historical replies gain a fork action

Kimi Code Desktop 1.3.0 added forking from past turns and running sessions on November 4, 2026. Selecting “从此处分叉” (fork from here) below a completed reply creates a session containing only that turn and earlier content. A running session can also be forked while the source session continues. This version requires macOS 13 or later. November 4 update

A fork is saved as a separate session that you can continue, with a “Fork: ” name prefix. It differs from the temporary, read-only side question on the right. How the two entry points differ

Why it matters | Compare approaches without restating the starting point

Suppose you have discussed two navigation options for an event-registration page, continued developing the first, and now want to explore the second. Fork from the turn where both options were established, then ask the new session to develop the second one. Decisions added later in the first discussion do not automatically become assumptions for the second route.

Forking selects conversation context. When comparing actual code changes, still check the project files and branches: independent sessions do not by themselves establish that the files they operate on are isolated.

How to use it | Choose the fork point, then give a new direction

  1. Find a completed historical reply. Click “从此处分叉” (fork from here) below the desired turn. Confirm the new session’s starting point, then give a new request, such as “Keep the earlier registration requirements, but develop the second navigation option.”
  2. Check what a running-session fork omits. Select “分叉会话” (fork session) from the session-row menu. The original task continues. The new session keeps the current user input but omits the unfinished reply and tool outputs. If you need the original task’s final result, wait for the turn to finish and fork from the completed point.
  3. Return to both sessions to compare them. Develop the second idea in the new session, then inspect the first result in the original one. Record each approach’s assumptions. You can also use the Fork action or /fork for the current session; that starting point differs from choosing a particular historical turn. Official fork actions and context rules