FAQ
Product version
What's the relationship between Kimi WebBridge and Kimi Browser Extension?
Kimi WebBridge has been renamed to Kimi Browser Extension, with new features including a browser sidebar entry, web action recording, and breaking down web pages into instructions. The way local Agents call the extension remains unchanged and can continue to be used; the new sidebar entry requires signing in with your Kimi account.
Using the sidebar
Does chat history sync with kimi.com and Kimi Desktop?
No. The sidebar chat history is stored only in the current browser, and each account keeps the 10 most recent chats by default. To keep content long term, click “Export” below a response to save it as a Markdown (.md) file.
Installation and Setup
Which browsers are supported?
Chrome and Edge are currently supported. We recommend using the latest version for the best experience.
When installing the extension, it says “Cannot add app from this website”?
Please make sure you install it from an official app store (Chrome Web Store or Edge Add-ons). If you cannot access the app store, use the manual installation method provided on the official website.
Installing Kimi Browser Extension on Windows reports: installation failed
Kimi Browser Extension supports Windows. You can run the installation command in PowerShell:
I've completed the installation steps, but it says it's incompatible with Chrome when I use it. What's going on?
If Kimi Browser Extension can open web pages normally, but operations such as snapshot, evaluate, screenshot, and click keep failing, the more common cause is a conflict with other browser extensions.
Crawler, website assistant, screen recording, and AI assistant extensions are especially likely to affect Kimi Browser Extension.
Try the following troubleshooting steps:
- Open your browser’s extensions management page
- Temporarily disable other extensions
- Keep only Kimi Browser Extension enabled
- Restart the browser and try again
- If everything works again, re-enable the other extensions one by one to identify the conflicting extension
Nothing happens after running the connection command?
Check whether your network connection is working properly. If the issue persists, restart Kimi Claw Desktop and run the command again.
Can I use it on multiple computers?
Yes. Kimi Browser Extension needs to be installed and configured separately on each computer.
Can’t find Kimi Claw Desktop?
Kimi Claw Desktop is Kimi Claw deployed on your local computer. Open Kimi Desktop, find Kimi Claw in the left sidebar, create a new Claw, and choose to deploy it to “My Computer”.
Connection and Usage
My local Agent cannot use the browser — how do I check the connection status?
- In the browser sidebar, open “Settings” → “Local agent remote control” and check “Connection”: if it shows “Not connected”, click “Connect” to try again.
- Kimi Work users can also check the “Connect service” status under “Settings” → “Automation” → “External browser”, and click “Connect” to retry.
Note: being able to open the sidebar does not mean the local Agent connection has been configured.
If Kimi Work or another local Agent fails to use the browser, first check the raw error returned by the tool. Common fields and messages point to different checks:
| Raw error field or message | Meaning and checks |
|---|---|
error.code is extension_not_connected | The local service received the request, but the browser extension is not connected. Check the browser and extension in step 1, then the address in step 4 |
Connection refused or Failed to connect when accessing the local service address | The call could not reach the local service. Check installation and startup in steps 2 and 3, then the address in step 4 |
daemon did not come up together with Port … is most likely held by another program during startup | The service failed to start, possibly because the port is in use. Verify this in step 5 and check the accompanying logs |
Work through these checks in order:
1. Is the browser open and the extension enabled?
Open Chrome or Edge with Kimi Browser Extension installed, and confirm it is enabled on the browser's extensions page. Then click “Connect” in Kimi Work or the extension settings.
2. Have you installed only the browser extension, without configuring the local Agent?
Both the browser extension and the local Agent connection components are required. In Kimi Work, find and install the Kimi Browser Extension plugin from the plugin marketplace, then follow its installation and connection instructions.
For another local Agent, or if the local service is not configured yet, click “Connect” in the extension settings and send the installation instructions from the dialog to your local Agent. Alternatively, copy the following prompt for your operating system:
macOS or Linux
Windows
Confirm installation and service startup succeeded, then check “Connection” again.
3. Is the installed local service actually running?
Installation does not mean the service stays running. In Kimi Work, first click “Connect” on the settings page above. For another local Agent, ask it to check the local Kimi Browser Extension service and start it if needed. Then click “Connect” in the extension settings. If startup fails, check for a port conflict.
4. Does the extension address match the local service?
Check “Settings” → “Local agent remote control” → “Connection address” in the extension. The default is ws://127.0.0.1:10086/ws. If you changed the service port, the extension must use the same port. Changing only one side prevents the connection.
5. Does the error mention a possible port conflict?
If startup reports Port … is most likely held by another program, ask your local Agent to check the actual port, the program using it, and the accompanying logs. The message indicates a possible conflict; it does not prove the cause. Once confirmed, follow the port guide below.
If you still cannot connect, use the extension's “Settings” → “Feedback” to provide your Kimi Work or local Agent version, browser and extension versions, a connection status screenshot, the complete error, and the steps you have tried.
What if the port is in use? How do I change the connection port?
The local connection service uses port 10086 by default. First identify the program using the port. If you can close that program, exit it and retry the connection. If it must keep running, follow the steps below to change the port.
Kimi Work 3.2.18 and other local Agents can use the same port change procedure. If you use an older Work version, first upgrade to 3.2.18 or later. The local Kimi Browser Extension service must be v2.0.22 or later.
You can change the port for both the local service and the browser extension. The example below uses 12086; ask your local Agent to confirm it is free first. Wait for running browser tasks to finish, as restarting the service interrupts the current connection.
1. Edit the local service configuration.
Open the following file, or create it if missing. Preserve existing fields and change only addr. If a configuration error appears, check the JSON syntax and that addr follows the address format below, then retry:
- macOS / Linux:
~/.kimi-webbridge/config.json - Windows:
%USERPROFILE%\.kimi-webbridge\config.json
2. Restart the local service and check its status.
Run the commands for your operating system, or ask your local Agent to run them:
Confirm the result shows running: true and port is 12086. If the old port remains or startup fails, resolve the service error first. Work reuses a healthy running service; saving the configuration or reopening Work does not automatically move that service to the new port.
3. Change the extension's connection address.
In the sidebar, open “Settings” → “Local agent remote control” → “Connection address”, enter ws://127.0.0.1:12086/ws, click “Test”, then “Save” after a successful test. Return to settings and confirm “Connection” shows “Connected”.
4. Tell your local Agent to use the new address.
In Kimi Work, reopen Work after completing the steps above, then click “Connect” under “Settings” → “Automation” → “External browser”. For another local Agent, tell it the local service now uses 127.0.0.1:12086 and to continue browser tasks using the actual port returned by status. extension_connected: true means the extension is connected. If it is false, check that the browser is open, the extension is enabled, and the address matches step 3.
To restore the default, set addr back to 127.0.0.1:10086, restart the service, then click “Reset to default” on the extension's “Connection address” page. First confirm that no other program is using 10086.
Will Kimi Browser Extension leak my login information?
No. Everything runs locally on your device. Your login state and web page content do not leave your device. The Agent can only access the operation results you authorize.
Why do operations sometimes fail?
Complex page structures or dynamic loading may cause operations to fail. Try simplifying your instructions, or ask the Agent to take a screenshot first to confirm the page state before performing the operation.
Working with Other Agents
Besides Kimi, which Agents are supported?
Kimi Browser Extension supports all Local Agents, including Claude Code, Codex, Cursor, Kimi Code, Hermes Claw, and more.
Is the setup the same for different Agents?
The configuration command is the same: run a single curl command to complete the installation. For details, refer to the Skill configuration method for each Agent.
Feedback and Help
If you encounter any issues or have suggestions, feel free to send us feedback.
The more complete your feedback, the faster we can locate and resolve the issue.
When sending feedback, please include:
- Browser version: for example, Chrome 124.0.6367.82
- Kimi Browser Extension version: available on the browser extensions management page
- The AI Agent you use: for example, Kimi Desktop, Claude Code, Cursor, etc.
- Issue description and screenshots: please describe the steps to reproduce the issue as clearly as possible
- Relevant logs (if any): available in the extension UI or the browser console
Was this article helpful?