BrowserClaw

BrowserPaw</h1>
  <p><b>Reliable browser automation inside the Chrome session you already use.</b></p>
  <p>
    <a href="./docs/MAP.md">Project Map</a> ·
    <a href="./docs/TOOLS.md">Tool Reference</a> ·
    <a href="./AGENT_CONFIG_GUIDE.md">Client Config</a> ·
    <a href="./README.zh-CN.md">Chinese (zh-CN)</a> ·
    <a href="./LICENSE">AGPL-3.0 license</a> ·
    <a href="https://github.com/GoldenLoaf24h/browserpaw/releases">Releases</a>
  </p>
</div>

---

## 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 loc