browserpaw

BrowserPaw Reliable browser automation inside the Chrome session you already use. Project Map · Tool Reference · Client Config · Chinese (zh-CN) · AGPL-3.0 license · Releases Why BrowserPaw

BrowserPaw runs as a Chrome MV3 extension plus a local Native Messaging bridge. It uses the browser profile you already have instead of copying profile data or starting a separate automation browser. MCP clients can inspect pages, act with bounded tools, and verify results without making a remote service the owner of your browser session.

The project separates three things that are often mixed together:Static operating guidance that teaches an agent how to use BrowserPaw.Durable task and page ownership, so parallel work does not silently take over user pages.Verified site skills, which are learned from successful tasks and reused only after independent validation. ⚡ What is BrowserPaw?

BrowserPaw is a Chrome extension and local MCP server. Its canonical tool names start with chrome_*, while each client may add its own namespace around them. The default core tool profile keeps discovery small; use CHROME_MCP_TOOL_PROFILE=full or chrome_tool_docs when a task needs the wider surface.

Two execution paths are available:

1. Deterministic tools and pipelines for indexed actions, forms, keyboard, uploads, downloads, screenshots, network work, and assertions. 2. chrome_act_toward_goal for a bounded local perception-action loop when an on-page goal is easier to describe than to decompose into every step.

The persistent browserpaw repl exposes the same execution service as small task, page, locator, skill, and help interfaces for multi-step code workflows. It is a documented BrowserPaw subset, not a claim of full Playwright compatibility. 🎯 Key capabilitiesSession reuse – Runs against the profile already open in Chrome; BrowserPaw does not copy your browser profile or move credentials into a second browser.Pruned, indexed DOM – chrome_read_dom assigns document-scoped references and reports action budgets, frame coverage, omitted regions, and truncation. A fast snapshot prioritizes the viewport and interactive targets.Strict, frame-aware actions – Explicit frame targets stay within that frame; ambiguous matches are rejected; nested OOPIF coordinates are projected through their actual renderer geometry.Card flattening and viewport virtualization – flattenCards collapses repetitive feed cards into one-line summaries; virtualizeViewport folds off-screen list items into count placeholders.Shadow DOM traversal – Recursively walks open shadow roots; closed shadow hosts are tagged and interacted with at the host level. Accessible names are extracted from icon-only buttons (aria-l