kimi-webbridge

# Kimi WebBridge Control the user's real browser (with their login sessions) via a local daemon at `http://127.0.0.1:10086`. ## Health check (always do this first) ```bash ~/.kimi-webbridge/bin/kimi-webbridge status ``` Then act on the result: - **`running: true` and `extension_connected: true`** — healthy. Proceed with the tool calls below. - **Anything else** (command not found, `running: false`, `extension_connected: false`, errors) — **Read `references/operations.md`** in this skill directory. It has the install / start / diagnose routing table. Don't guess fixes here — every non-healthy state is handled in `references/operations.md`. ## Tools | Tool | Args | Returns | Note | |------|------|---------|------| | `navigate` | `url`, `newTab`(bool), `group_title` | `{success, url, tabId}` | Always use `newTab:true` on first call. `group_title` sets the tab group's visible label | | `find_tab` | `url`, `active`(bool) | `{success, url, tabId}` | **Reuse an already-open tab** — pass any URL or domain; `active:true` picks the tab the user is currently viewing, default picks the leftmost match | | `snapshot` | — | `{url, title, tree}` with `@e` refs | **Accessibility tree** (text) — use this to read page content and locate elements | | `click` | `selector` (@e ref or CSS) | `{success, tag, text}` | Synthetic `el.click()` | | `fill` | `selector`, `value` | `{success, tag, mode}` | Works on `<input>`/`<textarea>` AND `[contenteditable]` (ProseMirror/Lexical/Slate). `mode` is...