Edge Kit Browser v3.5.6 - Firefox (WebDriver BiDi) + Chrome, video understanding, gameplay, native web seam

This commit is contained in:
2026-11-08 19:48:48 +03:30
commit 4da855f5e1
8 changed files with 1182 additions and 0 deletions
+56
View File
@@ -0,0 +1,56 @@
# Edge Kit Browser
Human-style browsing for AI agents — a zero-dependency [Cordis](https://github.com/moeru-ai) plugin for DeepSeek Harness that drives **Microsoft Edge, Google Chrome, or Mozilla Firefox** directly, with no extra services and no API keys.
The kit talks to the browser the way a person does: it *sees* the page (visible text + numbered actionable elements, shadow-DOM aware), *acts* (click, type, press, scroll — real input events), *verifies* (screenshots, wait-for-content), and *organizes* work across tabs. It also powers the harness's native `web_search` / `web_fetch` seam, so agents get clean, JavaScript-rendered content from signed-in or bot-walled pages.
## What it does
- **Human-style browsing** — `see`, `click`, `clickAt`, `drag`, `type`, `press` (real key codes + repeats), `scroll`, `waitFor`, `goto`, tabs, screenshots, raw `eval`.
- **Video understanding** — the `video` action enumerates players, reports full playback state (`playing`, `currentTime`, `duration`, `readyState`, geometry, source), controls them (`play`/`pause`/`seek`/`rate`), and captures PNG frames straight off the player region.
- **Gameplay** — correct key codes (Space is actually Space), coordinate clicks, and drags, plus before/after screenshots: agents can literally play a browser game and see what happened.
- **Native web seam** — registers `edge-kit` as a `web_search` / `web_fetch` provider: rendered-page extraction with dual-engine fallback (Google/Bing), no bot walls, no API keys.
- **Live-attach first** — if a debuggable browser is already listening, the kit attaches to it (borrowed browsers are never closed). Otherwise it launches: your signed-in profile (default) or an isolated kit profile.
## Install
Copy this package into your harness profile (or `pnpm install` it as a workspace link), then add to your composition:
```yaml
- insert:
- id: edge-kit-easy
name: "@local/edge-kit-easy"
config: {}
```
Optionally route the built-in web tools through the kit (pin the seam):
```yaml
- id: web
config:
fetchProvider: edge-kit
searchProvider: edge-kit
```
Settings live on the plugin's native page (**Plugins → Edge Kit Browser**); every field is volatile, so changes apply live without restarting the browser session.
## How it drives each browser
| Engine | Protocol | Launch flags | Port (default) |
|---|---|---|---|
| Edge / Chrome | CDP over WebSocket (`/json/version`) | `--remote-debugging-port`, `--user-data-dir`, anti-occlusion | 9444 (Edge) |
| Firefox | **WebDriver BiDi** (`/session`) — the kit contains a CDP→BiDi adapter | `-remote-debugging-port`, `-profile`, `-no-remote` | — |
Firefox (158+) exposes WebDriver BiDi on its debug port rather than CDP; the adapter translates every call transparently, including `session.status`/`session.new` handshaking, `script.evaluate` with `expression`, `browsingContext.captureScreenshot` (`{type:'box'}` clips), and load-event mapping.
Per-browser profiles: the user's real profile by default (`realProfile`), or isolated kit profiles under `~/.dsh/browser-profiles/edge-kit[-chrome|-firefox]`. If your everyday browser owns the profile, pass `relaunch: true` to restart it debuggable (logins survive) or set `profileDir`.
## Actions
`launch` · `attach` · `status` · `tabs` · `newTab` · `switchTab` · `closeTab` · `goto` · `back` · `forward` · `reload` · `see` · `click` · `clickAt` · `drag` · `video` · `type` · `press` · `scroll` · `waitFor` · `eval` · `screenshot` · `wait` · `close`
## Troubleshooting
- **`Maximum number of active sessions` (Firefox)** — a zombie Firefox is holding the BiDi session slot; terminate `firefox.exe` and relaunch.
- **DevTools port never opens** — your normal browser owns that profile: pass `relaunch: true` or a separate `profileDir`.
- **Screenshots black on headless/console sessions** — the kit launches with anti-occlusion flags and `fromSurface:false` to avoid this; on Firefox use the default screenshot path.