Kimi launches a browser extension that turns web actions into reusable Skills

Kimi now has a browser extension. According to a September 25 report from QbitAI, Moonshot has rebuilt the Kimi WebBridge it launched a few months ago into a "Kimi browser extension," and the biggest change is the entry point: instead of only being driven by a local agent, the extension can now be used directly from the browser sidebar.

Clicking the Kimi icon in the browser toolbar and signing in lets a user talk to Kimi in the sidebar and have it operate the current page, while the original route — a local agent calling the extension — remains available. Opening pages, reading content and clicking buttons all carry over from WebBridge.

Two capabilities are genuinely new. One is the sidebar itself. The other is recording: the extension can capture what a user does on a page and turn those steps into a Skill. A daily routine — open the same site, look up the day's news, export the data — can now be stored as a Skill and called again later, and if a session goes particularly well, Kimi can save that conversation as a Skill too.

The company frames this as making the extension better suited to repetitive work: available at hand, and repeatable.

The report is candid about the limits. Official guidance notes that site redesigns or dynamically loaded pages can still break a run midway, and suggests taking a screenshot to confirm page state before adjusting instructions when a complex page fails.

Seen against the short history of AI browser tools, the shift is a familiar one. An earlier generation — Monica, Doubao's plugin — was mostly about "reading the web": asking questions, translating pages, skimming papers. Manus's Browser Operator and Kimi WebBridge moved to "using the web," letting an agent drive the user's real browser with permission. Turning past workflows into Skills pushes one step further, toward accumulation.

Timing is part of the story. The extension lands right on the heels of Kimi Code Desktop, a workbench for agent projects whose built-in browser follows the project so changes can be checked immediately. One product points inward at the project; the other points outward at the Chrome or Edge the user already lives in.

What to watch next: whether recorded Skills stay reliable across sessions and how often they fail on frequently redesigned sites — and whether the extension gets wired more tightly into the Kimi Code Desktop workflow, so internal debugging and external browsing share one set of capabilities.