Kimi Work adds enterprise plugins, workspace switching and clearer network access recovery

The 3.2.18 and 3.2.19 desktop updates connect organisation-specific tools with visible task progress and an explicit response to IP restrictions.

Kimi Work's latest desktop updates add enterprise plugin creation, organisation-based workspace switching and more explicit handling of network restrictions. The changes arrived in versions 3.2.18 on 21 October and 3.2.19 on 22 October, according to Moonshot's official release notes.

The updates concern the working environment around Kimi's agent rather than a new model launch. They focus on how employees reach company tools, recognise the workspace they are using and follow a task while it is still running.

Organisation-specific tools in the marketplace

Enterprise users can now create custom plugins and upload them to the plugin marketplace. The following release adds a status card after a plugin is created or updated, with its icon and version refreshed in the conversation.

That gives a plugin two visible roles: it is an installed capability, and it is also an object whose state can be inspected during work. For a team maintaining its own connection to an internal service, a versioned card can make it easier to identify which tool definition a conversation is using after an update.

The change also moves part of the enterprise rollout into a familiar distribution surface. A company can package a repeatable capability for its staff instead of having each employee reconstruct the connection in a conversation. The release notes do not describe a new public entitlement or imply that every custom plugin is automatically available outside its enterprise context.

Switching workspaces with visible roles

The avatar menu now groups workspaces by enterprise and displays role labels. Users can switch between those environments from the same menu.

This is a small interface change with practical consequences for people who participate in more than one organisation. A task may use files, plugins and permissions associated with the selected workspace. Making the organisation and role visible gives the user more context before beginning the work, especially when a personal workspace sits beside an enterprise one.

Version 3.2.19 also introduces an explicit restricted-access page when an enterprise IP allowlist blocks a connection. The page offers retry or a return to the personal workspace. A separate network-diagnostics feature supports targeted troubleshooting.

Following work while it happens

The 21 October release improves previews of some tool results during task execution. It also displays elapsed task time at the top by default and adds a setting controlling whether the task process is shown.

Those controls support two different ways of using a desktop agent. Someone carrying out a short familiar task may prefer a compact conversation focused on the output. A person integrating a new company plugin may want to inspect intermediate results and see whether the operation is progressing. The application now makes more of that choice explicit.

The same release fixes Markdown-table scrolling, a first-open content-loss problem in some Markdown editors and a dashboard scrollbar issue. These are operational changes to the environment in which agent outputs are inspected and edited.

Taken together, the updates develop Kimi Work as an enterprise desktop workspace: custom capabilities can be distributed, the current organisation is clearer, and a blocked network path produces an actionable state. For teams evaluating the application, those are concrete client behaviours to examine separately from the capabilities of the model selected for a conversation.

Sources

- [Kimi Work Release Notes](https://www.kimi.com/en/help/kimi-work/release-notes) — Moonshot AI