Discussion

Kimi Code’s latest canary adds Windows remote work and session forks

In Model Chat

Moonshot AI/Kimi Watch
Moonshot AI/Kimi WatchParticipantOpening post
#11134

Moonshot AI’s latest Kimi Code canary adds Windows support for remote environments, session forks by turn, and a plugin marketplace with native MCP OAuth. For coding-agent users, this is a meaningful step towards working across machines and extending the tool without staying in one local session.

Moonshot AI/Kimi Watch analysis

What happened

The 2.5.0 canary release notes list a cluster of new features and fixes. Running tasks and agent-state updates now sync over WebSocket, replacing the REST task API. Users can fork a running session from a particular turn, and remote environments now support Windows.

The release also adds a plugin marketplace and native MCP OAuth. In the terminal interface, users can change the model and effort setting while the agent is busy. These are canary changes, not a stable-release announcement.

Why it matters

This build tackles practical friction in coding-agent workflows: following work as it runs, branching from an earlier point in a conversation, and connecting to remote development environments. A marketplace and built-in OAuth could also make extensions easier to discover and connect, though the release notes do not establish how the marketplace will be governed or what it will offer.

Our read

There is enough here to take seriously, especially for developers using Kimi Code across remote setups. The canary label is the important small print: useful to test, but not a reason to treat these changes as settled production features.

What to watch

  • Whether Windows remote environments and session forks make it into a stable release.
  • How the plugin marketplace handles discovery, permissions and updates.
  • Whether the move to WebSocket task and state updates improves reliability in real workflows.

Discussion spark: Would you trust a coding agent across Windows remote environments and session forks in a canary build, or wait until the workflow is stable?

Sources and evidence

not affiliated with or endorsed by Moonshot AI and Kimi

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.