
Weavetab
dev.weavetabPublished by weavetab.devv2.5.0Updated Oct 24, 2026
Open automation engine for AI agents. Control live browsers and desktop apps locally.
Overview
Local automation engine that lets an AI assistant drive live Chromium browsers and Electron desktop apps over Chrome DevTools Protocol.
- What you can do
- Read and inspect pages: semantic maps, element finding, scraping, screenshots, console and design extraction
- Interact with pages: click, type, type stored secrets, keys, pointer hover chains, select, fill, upload, scroll
- Navigate and manage environment: tabs, navigation, viewport, emulation, device detection
- Run automation missions: bursts, recordings, learned patterns, dialogs, clipboard, waits
- Inspect network and storage: request interception, cookies, storage, checkpoints, performance
- Produce documents and canvas output: office documents, PDFs, canvas and eval
- When to use it
- Useful when an assistant should operate a real browser session or a local Electron app (for example VS Code, Discord or Figma) rather than a headless script, including multi-step form filling, scraping and repetitive UI workflows.
- Requirements
- Runs locally as an npm package via npx, so Node.js is needed. A Chromium-based browser or registered Electron app must be running and reachable over local CDP. Optional configuration lives in a local config file, and stored secrets are kept in a local secrets file. Desktop only.
Installation
In SourceWeft
- Open Weavetab in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
The open automation engine for AI agents.
Control live browsers and desktop apps locally with instant execution.
[version] [license] [MCP] [Node] [tools]
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 by Weavetab, 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
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
Add to your MCP client config:
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:
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:
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.
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:
Register apps in ~/.weavetab/config.json:
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 to127.0.0.1with 256-bit shared-secret Bearer/handshake authentication andOrigin/Hostvalidation. No listener on external interfaces. - Policy Engine: Per-domain
allow/read-only/deny/auditrules under the top-levelpoliciesarray in~/.weavetab/config.json(blocks*.bank.*andpaypal.comout 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.jsonpermission 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_<timestamp>.log
Security vulnerabilities: [email protected] (do not use public issues).
CLI Reference
Configuration file: ~/.weavetab/config.json
Extensibility
Weavetab exposes a typed Plugin SDK for authoring custom MCP tools, HUD overlays, and tool lifecycle hooks:
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.
For commercial embedding, closed-source SaaS, or proprietary enterprise licensing, see COMMERCIAL.md or contact [email protected].
Source: README.md at commit 129314c
Tools
0Version history
1- v2.5.0LatestOct 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts