Kimi Code 0.42.0 makes Remote Control and model routing default

Moonshot’s Kimi Code CLI 0.42.0 makes Remote Control and the subagent model pool standard features, adds direct X11 clipboard support to the terminal interface, and brings plugin management to the browser UI. The release also updates transcript rendering, side-agent tools, media attachments, and long-file reads. Developers using experimental environment variables should remove the retired switches from their configurations. Moonshot lists every change in the release notes.

Two experiments become defaults

Remote Control is now available without setting KIMI_CODE_EXPERIMENTAL_REMOTE_CONTROL, which has been removed. The feature provides access to a local Kimi web session from another machine. Developers can start it with kimi rc, kimi web --remote-control, or the /remote-control command inside a running session. Setup instructions are available in the Remote Control guide.

The subagent model pool is also enabled by default. Moonshot removed the experimental secondary-model control and the KIMI_CODE_EXPERIMENTAL_SECONDARY_MODEL opt-out. The main agent can route subtasks to different models according to the descriptions declared under [secondary_model] in config.toml. A project might assign routine refactoring to a faster model while reserving a stronger model for difficult debugging work.

Shell profiles, CI variables, container definitions, and dotfiles that set either retired environment variable should be updated. Existing [secondary_model] configuration remains relevant because it defines the models available for task routing.

X11 gets a direct clipboard path

Kimi Code’s terminal UI now supports the Linux X11 clipboard directly. Copying previously relied on OSC 52, an escape sequence that asks the terminal emulator to place text on the system clipboard. Terminals without OSC 52 support could leave TUI copy operations unreliable or unusable.

The new X11 integration removes that terminal dependency for X11 sessions. Wayland behavior is unchanged and continues to use the existing clipboard path.

Plugin management moves into Settings

The kimi web interface now includes a Plugins panel under Settings. From the panel, developers can browse the plugin marketplace and install, enable, disable, or remove plugins without returning to the terminal.

Plugin management remains available through the /plugins command, while the new panel gives browser-based workflows access to the same core controls.

Transcripts, media, and file reads improve

• Completed tool calls collapse to a header and one marked outcome row. Short output remains visible, hidden output shows a count such as N more lines or +N more, and Ctrl-O reveals the full result.
• The /btw side agent can use read-only tools, allowing its auxiliary conversation to inspect project files while the main task continues.
• The web composer displays attached images and videos in a reorderable media rail. Users can reference attachments in the prompt, and previews remain visible after content is queued or sent.
• File reads support configurable character limits and can resume after encountering long lines, preventing repeated truncation at the same point.
• Prompt attachments and ReadMediaFile now accept HEIC, HEIF, and BMP images when the selected model is served by Kimi.

Upgrade and configuration cleanup

Developers can install version 0.42.0 with kimi upgrade or use the standard installation script from the GitHub repository. Kimi Code remains available at no charge with a Moonshot account.

• Remove KIMI_CODE_EXPERIMENTAL_REMOTE_CONTROL from local and automated environments.
• Remove KIMI_CODE_EXPERIMENTAL_SECONDARY_MODEL and any retired experimental secondary-model control.
• Keep and review [secondary_model] entries that describe how the agent should route subtasks.
• Linux X11 users can use TUI copy operations without requiring OSC 52 support from the terminal emulator.

Version 0.42.0 reduces the configuration needed for remote sessions and multi-model routing while closing specific gaps in Linux clipboard handling and browser-based plugin management. The migration work is limited to deleting obsolete experimental controls and retaining any model-pool definitions the project still uses.