Kimi Code Desktop: Multi-Directory Projects and Session Forks

Group related directories in one project

The Desktop 1.3.0 release notes dated November 4, 2026 introduced improvements including multi-directory projects and session forks. A project groups local working directories: choose a primary directory, then add related source folders. When editing it, you can rename the project, add or remove directories, or import legacy additional directories from .kimi-code/local.toml in the primary directory.

Sessions, drafts, file previews, and terminals are isolated by project. When a project has multiple directories, choose Switch file tree root at the top of the file tree to browse another directory; this changes the directory shown in the tree.

Open Show session information from the session title; the right panel lists each directory's primary marker, branch, ahead/behind status, changes, and PR. These indicators help you identify what to inspect, but they do not prove that tests passed or a change was published.

Choose a local working directory for the session

After creating a session, click the folder name above the Composer to open the workspace picker. Choose a recent directory or select Choose folder… to add another local one. Choose Enter an absolute path directly to enter a local absolute path, or drag a folder from Finder or File Explorer onto the sidebar.

The new folder is added to the current project and the recent-folder list. An empty session needs a working directory before you can send a message. If you open an untrusted folder, the app asks whether to trust it; declining blocks messages in that workspace. Before sending a task, check the directory shown above the Composer so it goes to the intended project location.

Fork from a completed historical turn

To continue from a completed answer in a different direction, choose Fork from here below that turn. The new session retains the selected turn and the conversation before it; creating the fork leaves the original session unchanged. You can also fork from a session item or type /fork in the Composer to copy the current session.

The fork is saved separately with a Fork: prefix, so both conversations can continue. The documentation defines a conversation copy; it does not establish that Fork creates a Git branch or worktree, restores files, or isolates concurrent file edits. Handle file versions and isolation separately through the project’s existing Git and backup process.

A running-session fork keeps the current prompt

If the source session is still running, open that row's menu in the session list and choose Fork session. The source continues executing. The new copy keeps the current user prompt but does not include the unfinished response or tool output.

The fork does not replace the source session or show what its still-running operation eventually did. Return to the source to see its later response. Use a fork to preserve the current conversation point and explore another direction.

Use side chat for temporary, read-only discussion

Choose New conversation in the right panel to open a temporary side chat based on the main session's context. It can use read-only tools, cannot modify files, and is not saved as a regular session; once you close the tab, you cannot recover its contents.

Use Fork when you need a saved conversation copy that you can continue. Use side chat for a temporary question about the current context when you do not want to interrupt the main session. Their save behavior and tool access differ, so a side chat is not a saved fork.

Check requirements and prepare diagnostic information

The current Quick Start lists macOS 13.0 or later (Apple Silicon and Intel), 64-bit Windows 10 or later, and x86_64 Linux as the minimum system requirements; macOS 12 no longer receives updates. Official Kimi models require a signed-in Kimi account with a membership, and available models vary by plan. Third-party model providers are configured separately. The sources do not establish regional eligibility or separate workspace or fork pricing, so check the terms for your account and provider.

For a slow or failed startup, a white screen, an internal error, or an unexpected exit, choose Help → Export Diagnostics… from the app menu or system-tray menu. The ZIP is saved to your system Downloads folder and includes logs, startup state, white-screen snapshots, and local crash reports from the last 30 days. The startup loading page also offers export, opening the log folder, or restarting the app.

The package contains local logs and crash information, so review its contents before sending it to official support. Exporting diagnostics gathers troubleshooting material; it does not mean the package has been automatically cleaned or is suitable for public sharing.