Weavetab

The open automation engine for AI agents. Control live browsers and desktop apps locally with instant execution.

Tool Reference · Documentation · Architecture · Support · Security

---

Weavetab is the open automation engine for AI agents. It connects models directly to live Chromium browsers and Electron desktop applications via native Chrome DevTools Protocol (CDP) sockets — no WebDriver binaries, no cloud relay, zero telemetry.

Actions execute directly over local CDP sockets without external driver overhead. Web pages are translated into agent-readable semantic maps with turn-by-turn diffing that reduces token usage by up to 95%. Built-in security enforces local domain policies, role-based access control, and client-side credential injection.

Built and architected by fy2ne.

---

Why not Playwright or Puppeteer?

The standard approach — Playwright over MCP — works. But it carries fundamental architectural costs that compound at scale.

---

Architecture

MCP Client (Claude / Cursor / Antigravity / Copilot / Windsurf)

| | JSON-RPC 2.0 (stdio or WebSocket 127.0.0.1:3000) v +-------------------------------------------------------------+ | Weavetab MCP Server | | | | +-----------------+ +---------------------------------+ | | | Security Layer |-->| Intelligence Engine | | | | Rate · RBAC | | Map 3.0 · Delta · Memory | | | | Policy · Audit | | Pruner · Framework Detector | | | +-----------------+ +----------------+----------------+ | | | | | +----------v----------------+ | | | CDP Bridge | | | | Ghost Cursor · Typing | | | | App Router · Loop Guard | | | +----------+----------------+ | +-------------------------------------------------------------+ | CDP WebSocket (127.0.0.1) +---------------------------+-----------------------------+ v v v Chrome / Edge VS Code / Discord Your Electron App (any tab) (Electron apps) (local dev)

No cloud. No external process. Both the CDP WebSocket connection and the optional MCP WebSocket daemon (--ws) are strictly bound to 127.0.0.1 with shared-secret authentication (~/.weavetab-system/ws-secret) and Origin/Host header verification.

---

Quick Start

npx -y @weavetab/mcp

Add to your MCP client config:

{

"mcpServers": { "weavetab": { "command": "npx", "args": ["-y", "@weavetab/mcp"] } } }

---

Core Technology

Semantic Map 3.0

The primary bottleneck in browser-based agents is DOM representation. Full HTML dumps are noisy, large, and structurally meaningless to language models. Weavetab's browser_map runs an in-browser CDP walker that produces a compact semantic map:

╔═ ACTIVE DIALOG: "Confirm Payment" ═╗

[w:3] button "Confirm" [w:4] button "Cancel"

┌ "Pro Plan — $49/mo" [w:12] button "Upgrade" [w:13] button "View Details" [w:14] input val:"john@example.com" ph:"Email address" FOCUSED

[w:20...w:38] 18 nav links: "Dashboard" ... "Sign out"

Key properties:

• Ref IDs (w:N) are stable within a session and used by all interaction tools
• Container binding — buttons and inputs are grouped under their parent card, row, or section header
• Modal hoisting — open dialogs are isolated at the top so agents cannot miss them
• Link collapsing — repeated nav/footer runs of 4+ links compress into a single token line
• Semantic delta — on re-reads, only changed nodes are transmitted (~ modified, + added, − removed), cutting re-read cost by up to 95%

Ghost Cursor

Clicks are not dispatched as synthetic DOM events. They are delivered as a physical sequence of Input.dispatchMouseEvent CDP calls along a Bezier curve trajectory with randomized acceleration, natural jitter, and hold durations. Anti-bot fingerprinting that flags event-based automation does not trigger.

browser_pointer supports hover_chain for multi-level menu traversal in a single tool call:

{

"hover_chain": ["File", "Export As", "PNG"], "click_final": true }

Blind Credential Injection

browser_type_secret resolves secrets server-side from ~/.weavetab/secrets.json. The resolved value is never included in the MCP response, never appears in DOM snapshots, and is permanently masked as [REDACTED] in all audit logs. The LLM context never sees the credential.

weavetab secrets set GITHUB_TOKEN

Stored. Never echoed, never logged, never surfaced to the agent.

Electron & Desktop App Automation

Any tool accepts an optional app parameter that routes the command to a registered Electron process instead of a browser tab:

{ "app": "discord", "ref": "w:24", "text": "Hey, deploying now" }

Register apps in ~/.weavetab/config.json:

{

"electron": { "discord": "C:\\Users\\ \\AppData\\Local\\Discord\\Discord.exe", "vscode": "C:\\Users\\ \\AppData\\Local\\Programs\\Microsoft VS Code\\Code.exe", "figma": "C:\\Users\\ \\AppData\\Local\\Figma\\Figma.exe" } }

Weavetab auto-attaches via CDP to the registered process. No code changes required in the target application.

Zero-API CAPTCHA Solving

browser_captcha solves Cloudflare Turnstile, reCAPTCHA v2/v3, GeeTest, and hCaptcha by orchestrating CDP mouse events that replicate human behavioral signatures — velocity curves, micro-pauses, scroll inertia — with no third-party API, no external service, and no API key required.

---

Tool Suite

41 tools across 9 categories. Full parameter reference: docs/tools/tools.md

---

Security

• Transport: Both CDP WebSocket and MCP WebSocket daemon (--ws) are strictly bound to 127.0.0.1 with 256-bit shared-secret Bearer/handshake authentication and Origin/Host validation. No listener on external interfaces.
• Policy Engine: Per-domain allow / read-only / deny / audit rules under the top-level policies array in ~/.weavetab/config.json (blocks *.bank.* and paypal.com out of the box)
• RBAC: Five roles — operator (default), viewer (least-privilege read-only), automation, system, admin — enforce tool-level permission gates
• Plugin Trust & Manifests: 3-tier verification (@weavetab/* official, verified registry allowlist, and mandatory interactive confirmation + weavetab.json permission manifest inspection for unverified packages)
• Blind Injection: Credentials resolved server-side, masked in all outputs and audit logs
• Loop Breaker: Strike-based stuck-loop detector halts runaway autonomous sequences
• Audit Log: All tool invocations, policy decisions, and errors written to ~/.weavetab-system/logs/mission_ .log

Security vulnerabilities: security@fy2ne.me (do not use public issues).

---

CLI Reference

weavetab                        # Start in stdio mode (default)

weavetab --ws --port 3000 # WebSocket daemon mode (bound to 127.0.0.1) weavetab config # Interactive configuration wizard weavetab secrets set KEY_NAME # Store a secret (never echoed) weavetab secrets list # List stored secret keys (not values) weavetab plugin add # Install a verified/confirmed plugin weavetab plugin list # List installed plugins

Configuration file: ~/.weavetab/config.json

{

"browserType": "chromium", "headless": false, "extension": true, "maxActionsPerMinute": 60, "role": "operator", "electron": { "discord": "...", "vscode": "...", "antigravity": "..." } }

---

Extensibility

Weavetab exposes a typed Plugin SDK for authoring custom MCP tools, HUD overlays, and tool lifecycle hooks:

npx @weavetab/sdk init my-plugin

See docs/PLUGINS.md for architecture, manifest spec, and SDK API reference.

---

License

AGPL-3.0-only. Client connections over stdio or WebSocket do not extend copyleft obligations to your client application or models.

[Sponsor development](https://github.c