Browser Harness
Browser Harness is a thin, self-healing harness for browser agents built directly on CDP. Agents can edit their own helpers mid-task, so the harness improves with every task and enables LLMs to complete browser tasks.
Visit browser-use/browser-harnessOverview
Browser Harness is a thin, self-healing harness built directly on CDP. It connects an LLM to a real browser through one editable CDP websocket, and the agent writes missing helpers as it works so the harness improves with every task. It can run on local Chrome, stealth browsers, or a Browser Use Box, and it offers an MCP server for MCP clients.
Key Features
- Thin self-healing harness built directly on CDP.
- Connects an LLM directly to a real browser through one editable CDP websocket.
- Agents write missing helpers mid-task in their local workspace, so the harness improves with every task.
- Protected core source stays separate while agents write reusable helpers.
- MCP server browser-harness-mcp exposes browser control helpers as MCP tools over stdio.
- Can run on local Chrome, stealth browsers, or 24/7 on your own Browser Use Box.
Use Cases
- Complete browser tasks such as opening a profile, finding the latest 20 video posts, and downloading them.
- Handle logged-in, personal browser work with a local browser.
- Scale many browsers in parallel with live previews, proxies, stealth, and CAPTCHA solving through Browser Use Cloud.
- Drive the browser from MCP clients such as Claude Code, Devin, and Cursor without writing a second CDP layer.
Getting Started
- Paste the provided setup prompt into Claude Code or Codex.
- Install or upgrade browser-harness to the latest stable version with uv using Python 3.12.
- Register the skill from browser-harness skill and connect it to your browser.
- On first setup, tick the checkbox in chrome://inspect/#remote-debugging so the agent can connect to your browser.
- If setup or connection fails, follow install.md.
Before You Adopt
- License: MIT. Review its terms before using, modifying, or distributing the project.
- First-time connection to a local browser requires enabling remote debugging in Chrome.
- Local browser recordings are optional and default to off, with existing preferences preserved on upgrades.
- Scaling to many parallel browsers depends on Browser Use Cloud for features such as live previews, proxies, stealth, and CAPTCHA solving.