Kimi Code built-in browser or WebBridge?

Kimi Code can use Kimi Browser Extension, the updated name for WebBridge, when you want its local agent to control an existing Chrome or Edge session. Kimi Code CLI can also discover shared Agent Skills, including a local Tabbit skill, and invoke one with /skill:tabbit. That is a separate route: it asks the local Tabbit CLI to work in Tabbit Browser. Check which browser profile owns the login before asking either tool to inspect a page.

A Reddit user says WebBridge worked with existing tabs after adding a compatible skill; another reports that an extension badge looked active while Kimi Claw said the bridge was offline. The reports concern different clients and do not establish Kimi Code or Tabbit compatibility by themselves. They do show why you should check both the client connection and the target page. (r/codex, r/kimi)

Key takeaways

• Kimi Code officially supports Kimi Browser Extension, formerly WebBridge, for real Chrome or Edge sessions.

• Kimi Code CLI supports Agent Skills in ~/.agents/skills/ and the /skill:<name> command.

• Tabbit uses its own installed tabbit-cli and Tabbit Browser profile. A Kimi extension connection does not connect to Tabbit.

• Confirm the client can run a local command, the browser runtime is reachable, and the selected page is the intended signed-in session.

• Start with a read-only capture. Name the draft and require a human review checkpoint before any external action.

Choose the browser route by session

Kimi's help page says the renamed Kimi Browser Extension supports local agents including Kimi Code. It lists Chrome or Edge on macOS or Windows. Install and connect the extension in the profile that owns the authorized session; the browser extension setup and Kimi Code's Skill catalog are separate configuration steps. (Kimi Browser Extension)

For Tabbit, Kimi Code CLI's Agent Skills documentation lists ~/.agents/skills/ as a user-level scan directory and gives /skill:<name> as the manual invocation format. The Tabbit skill then calls the locally installed tabbit-cli. Skill discovery does not prove that Kimi Code can execute shell commands in your policy, that the Tabbit launcher is installed, or that the chosen runtime is reachable. Check those independently.

Capture a page with Tabbit and leave a review draft

Use this route when the page is already open in Tabbit or you want the task to run in Tabbit's browser profile. Keep the capture narrow: final URL, page title, one safe visible heading or marker, and the source label. Do not return a full page dump when the task only needs a source excerpt.

/skill:tabbit Capture the title, final URL, and the visible heading from the page I identify. Use one task tab. Save a draft named "Kimi source check: Q4 returns policy" with the source URL, capture time, excerpt, and a line labeled "Human review". Do not submit forms or change the page. Stop if the URL or heading does not match the source I named.

The prompt is a local-agent workflow example. It does not claim that Kimi WebBridge controls Tabbit. Tabbit CLI tasks run in separate task tabs, which lets you keep working in other browser tabs and review the draft when it is ready. Read how to connect an agent to an existing browser and the browser agent first-task checklist before using a signed-in account.

What to check before relying on the capture

For tasks in Kimi Code Desktop, its built-in browser documentation describes a separate browser for local previews. The Kimi Code settings and extensions guide describes the product's extension and Skill settings. Neither changes which profile the Tabbit CLI uses.

The broader browser profiles and task tabs guide explains why two windows can show different sign-in states. If you only need public pages, use the browser research workflow. For another CLI setup with Tabbit, see Codex and Tabbit CLI. These are related routes, not evidence of a Kimi extension integration.

For a comparable existing-session example, see the Codex signed-in dashboard workflow, the DeepSeek Harness plugin guide, and the OpenClaw browser setup. Each uses a separate client connection.

Frequently asked questions

Can Kimi Code use Kimi Browser Extension?

Yes. Kimi's extension help lists Kimi Code as a supported local agent. The extension is now called Kimi Browser Extension and was formerly called Kimi WebBridge. Follow the current extension install instructions and check its local-agent connection.

How do I invoke Tabbit from Kimi Code CLI?

Make the Tabbit skill visible to Kimi Code, confirm its local shell policy permits the required command, then enter /skill:tabbit. The skill's existence alone does not confirm that the Tabbit CLI or browser runtime is available.

Does WebBridge control Tabbit Browser?

No. Kimi Browser Extension connects to its supported Chrome or Edge profile. Tabbit CLI controls Tabbit Browser through the installed local launcher. These are distinct browser routes.

Can the agent reuse a website login?

It can only use a login in the browser profile it can reach. Open the authorized page in the intended profile and verify the final URL and a safe visible marker before asking for an excerpt.

Can I keep using my browser during a task?

With the Tabbit CLI workflow, the agent runs in task tabs separate from your other browser tabs. Do not let it claim or change an unrelated tab. Review the output before you use it.

What belongs in a review draft?

Keep the draft focused on the source URL, capture time, requested excerpt, and a human-check line. Do not include passwords, cookies, authentication codes, or unrelated private page content.

Secholar.L

Growth & Content at Tabbit

Secholar.L writes hands-on guides about AI browsers and agent workflows, comparing tools with real research and citing verifiable sources.