Kimi WebBridge becomes a browser-side assistant

Moonshot AI has renamed Kimi WebBridge to the Kimi Browser Extension and added a sidebar for controlling websites through chat. Users can ask Kimi to navigate pages, enter data, and complete multi-step workflows, then save recorded actions as reusable skills.

For developers, the release adds a user-facing entry point without replacing the existing local bridge. Supported coding agents can continue controlling Chrome or Edge through the same integration, and recorded skills reduce the need to describe recurring workflows in every prompt.

The bridge gets a sidebar

The original WebBridge focused on developer tools such as coding agents and command-line assistants. It paired a browser extension with a local background service, giving those agents access to an existing browser session. The renamed product retains that architecture and adds direct interaction through a sidebar tied to a Kimi account.

Four changes shape the release

How commands reach the page

The extension and its local background service communicate with Chrome or Edge through the Chrome DevTools Protocol. CDP is the browser control interface used by developer tools and automation frameworks. It can open pages, click elements, scroll, type, capture screenshots, and inspect page content.

1. A user sends a request through the Kimi sidebar, or a supported external agent calls the bridge.
2. The agent converts that request into browser actions.
3. The local service sends those actions to the existing browser session through CDP.
4. The extension returns page state, extracted content, or screenshots needed for the next step.

Browser actions execute on the local machine, and authentication cookies remain in the browser profile. Data can still leave the machine when page text, screenshots, or prompts are sent to Kimi or another model provider. The effective privacy boundary therefore depends on the selected agent, model endpoint, account settings, and requested task.

Local sessions change the trade-offs

Using an existing browser profile preserves logged-in sessions and can reduce repeated authentication during automated workflows. It also avoids transferring raw session cookies into a separately hosted browser. Websites may still present CAPTCHAs, require fresh multifactor authentication, or block automated behavior.

Access to an authenticated profile gives the agent substantial authority, so deployments should limit that authority deliberately:

• Use a separate browser profile for automated work.
• Keep banking, email, administration, and production consoles outside that profile.
• Require confirmation before purchases, messages, submissions, deletions, or account changes.
• Treat page content as untrusted because malicious text can attempt to redirect an agent through prompt injection.
• Review extension permissions, model retention policies, and logs before handling confidential data.

One bridge, several agents

Moonshot lists support for Kimi Code CLI, Claude Code, Cursor, Codex, and Hermes. During setup, the installer can place the relevant skill definitions into supported agent environments, allowing those tools to discover the browser interface without a custom adapter.

The agent-neutral interface gives teams a common browser layer across multiple model providers. Model quality, tool-calling behavior, context limits, and usage charges still vary by provider, so the same recorded workflow may need testing with each agent.

Recorded skills suit stable routines

Good candidates for recording include collecting research sources, filling predictable forms, comparing product listings, compiling job posts, and gathering data for analysis. A saved skill can preserve the steps and expected sequence, making repeated runs more consistent than starting from a fresh natural-language request.

Recorded actions remain sensitive to website changes. Revised layouts, renamed controls, dynamic content, and new authentication checks can interrupt playback. Workflows that publish content, move money, or modify records should include validation and a human approval step before the final action.

Installation has two parts

The setup requires the Chrome or Edge extension plus Moonshot’s local bridge service. Distribution links for the browser add-ons and the macOS desktop application are available from the product page.

Moonshot provides the following PowerShell command for Windows:

irm https://kimi-web-img.moonshot.cn/webbridge/install.ps1 | iex

Because the command downloads and immediately executes a remote script, developers should inspect the script and verify its source before running it. macOS users install the Kimi Desktop App, which supplies the local component used by the extension.

Moonshot lists the extension and local service as free. Kimi subscriptions, API usage, or charges from another connected model provider may still apply.

Where it fits in an agent stack

Browser agents generally rely on either hosted browser sessions or software attached to a local browser. Moonshot’s design favors the second approach, combining an authenticated local session, an interface for several agents, a Kimi sidebar, and recordable workflows.

Evaluation should focus on the data sent to the selected model, the permissions granted to the extension, recovery from changed page layouts, confirmation controls for consequential actions, and compatibility with existing agent tooling. Those factors determine whether the extension is suitable for routine browsing, internal automation, or higher-risk authenticated workflows.