Start with Kimi Code’s built-in browser for local previews. Use the Kimi WebBridge plugin with Kimi Browser Extension if a task needs the Chrome or Edge profile where you already signed in. If the same URL opens a dashboard in one window and a sign-in form in another, first check which session opened each page. If you want to do the page check in Tabbit Browser, there is a separate example below.
One r/codex user reported that the extension worked with existing tabs after adding a compatible skill. A r/kimi user reported that Claw said the bridge was offline even though the extension looked active. The reports describe different clients. Together they illustrate why a badge and an existing session are different checks. Use a minimal read-only marker before proceeding.
Key takeaways
Use the built-in browser to preview a local app and keep page feedback in the current coding session.
Use the WebBridge plugin and browser extension when the task needs an existing Chrome or Edge login.
Kimi lists macOS and Windows for the extension setup. Check the profile and local-agent connection separately.
Before using a signed-in page, match its final URL and a safe visible marker.
Use the built-in browser for a session preview
In Kimi Code Desktop, open the right panel, choose New tab and select Browser. The desktop File menu also offers New Browser Tab. Paste the exact preview URL or ask the agent to open it. Tabs stay with that Kimi Code session, and the built-in browser offers inspection, annotation and manual takeover. For localhost, verify the service address and port from its startup output.
| Entry | Session source | Main use | Limit |
|---|---|---|---|
| Built-in browser | Current Kimi Code Desktop session | Preview a local app and annotate page elements | Existing Chrome or Edge login belongs to a separate profile |
| WebBridge | Profile where Kimi Browser Extension is installed | Use an existing Chrome or Edge login | Requires the extension and local-agent connection |
Kimi Code Docs · Built-in Browser Kimi Code Docs · Browser image
Site sign-in follows the profile. Learn how that differs from workspaces and tab groups.
Browser control in DeepSeek Harness also starts by choosing where the browser runs.
Choose WebBridge when the profile matters
Open Settings > Plugins in Kimi Code Desktop and look for the official Kimi WebBridge plugin. The current product page calls the browser component Kimi Browser Extension. Kimi's desktop guide points to Chrome or Edge when the browser extension is missing. Install it in the profile that owns the approved session and complete the connection steps from the official extension settings.
Kimi Code Docs · Settings and Extensions Kimi Code Docs · Settings image
An agent can only use a signed-in page if it can reach the right profile. See connecting an agent to existing tabs.
Kimi lists Chrome and Edge on macOS and Windows for the extension setup. The Kimi Code Desktop download guide separately lists macOS, Windows and x86_64 Linux. The extension FAQ mentions a Linux service path, but the extension requirements table lists macOS and Windows. Kimi Browser Extension · Kimi Code Desktop.
OpenClaw exposes a similar profile decision in the OpenClaw browser setup guide.
Check the specific browser session
Opening the sidebar confirms that the browser extension interface is present. It does not establish that your local agent connected. Check the extension's local-agent connection status and make sure Kimi Code is enabled in its local-agent section when that option is offered. Reload or start a new agent session if the connection or plugin is not visible. Select a known page by its full URL and visible marker before relying on its authentication.
Add the URL and marker checks to your browser agent setup checklist.
Try the same read-only page in both paths
Use a site you control that displays either Sign in or a test dashboard marker, without personal content. Open its exact URL in the built-in browser and record what is visible. Then use WebBridge in the intended test profile and record the final URL, heading and marker again. If one path shows a login page, pause and record it. Do not send passwords, authentication codes or cookie values to the agent.
The same sign-in distinction comes up in Codex’s signed-in dashboard example.
Using Tabbit for the same kind of task
For a read-only page check in Tabbit, give the agent one owned tab and ask for the final URL and heading. This uses Tabbit’s own browser controls. Kimi’s extension setup lists Chrome and Edge.
In Tabbit, open the approved page and assign its tab to the agent. Ask it to return the final URL, the heading and whether the page says Sign in or shows the expected test marker. Stop at the first mismatch. For a browser task that can stay in Tabbit, this keeps the handoff to one tab.
The comparison between Codex and Tabbit CLI shows how the two select tabs. For other uses, see the agent browser guide.
Pick the entry by task
| Task | Entry to use | What to check |
|---|---|---|
| Review a local preview | Built-in browser | The app is listening on the exact host and port |
| Read an approved dashboard | WebBridge | The signed-in profile shows the expected page marker |
| Compare page state across profiles | Both, separately | Record the final URL, heading and marker for each |
If the job is to check your code change, start in the built-in browser. If the job depends on a login you already have, start with the extension in that profile.
If the task can stay in Tabbit Browser, the same one-tab read-back gives you a quick way to check the page before any action.
FAQ
Why does the built-in browser show a login screen?
It opens the page in the desktop app’s own browser session. For an existing Chrome or Edge login, use WebBridge in that profile.
How do I open the built-in browser?
Use the plus button in the right panel and select Browser. You can also choose File > New Browser Tab.
Where is WebBridge configured?
Install Kimi WebBridge from Settings > Plugins. Add Kimi Browser Extension to the Chrome or Edge profile the task will use.
How can I verify the correct session?
Check Connection under the extension’s local-agent settings. Ask Kimi Code to report the final URL and a safe visible marker from the intended tab.
How do I test the sign-in difference?
Open the same test URL through each entry and record whether it shows a sign-in form or the expected marker. Use a page you control.
Which browsers and operating systems does Kimi list?
The extension requirements list Chrome or Edge on macOS or Windows. Kimi Code Desktop separately offers an x86_64 Linux installer.