browser-use /browser-harness

Let Claude Code, Codex or Cursor use your real Chrome, logged in as you. One prompt to set up. Open source, MIT.

★ 19,091⑂ 1,894👁 50⑃ 900● 110▤ 14
PythonMITCreated 2026-04-17browser-harness.com
Download: v0.1.13v0.1.13 ↓0.1.132026-09-04
+11
Daily
19,091
stars
1,894
forks
50
watchers
900
prs
110
issues
14
releases

README

[!NOTE]
 Browser Harness is now the engine inside Browser Use. Use the browser-use CLI: same helpers and daemon, plus browser-use login, an MCP server (browser-use --cli-mcp) and browser-use skill install.

 bash
 uv tool install browser-use
 browser-use  new_tab("https://example.com")
 print(page_info())
 PY
 

 The browser-harness command keeps working. Domain skills and interaction skills stay in this repo.

 Browser Harness ♞

Browser Harness lets Claude Code, Codex or Cursor use your real Chrome browser: open pages, click, type, read and download, logged in as you. Paste one prompt into your coding agent to set it up. It talks to Chrome over the DevTools Protocol (CDP), and the agent writes any missing helper as it works, so the harness gets better with each task. Open source, MIT licensed.

Try browser-harness in Browser Use Cloud or paste the setup prompt into your coding agent.


  ● agent: wants to upload a file
  │
  ● agent-workspace/agent_helpers.py → helper missing
  │
  ● agent writes it                         agent_helpers.py
  │                                                       + custom helper
  ✓ file uploaded


You will never use the browser again.

 See it work

Task: "Open my X profile, find my latest 20 video posts, and download them."



 Setup prompt

Paste into Claude Code or Codex (Cursor: use the MCP config below):

text
Install browser-use with uv tool install browser-use, run browser-use skill install to register the skill, and connect it to my browser. If setup or connection fails, run browser-use --doctor and follow its output and the error message.


The agent will open chrome://inspect/remote-debugging. On first setup, tick
the checkbox so the agent can connect to your browser:



 How it works

- install.md connects the agent to your browser.
- SKILL.md teaches it the browser workflow.
- src/browser_harness/ stays protected while the agent writes reusable helpers in its local workspace.

 Compared with other browser tools

| | Works with | Browser it drives | What you approve in your own Chrome |
|---|---|---|---|
| Browser Harness | Claude Code, Codex, Cursor, any MCP client via browser-harness-mcp | Your running Chrome, logged in as you | Whole browser: on Chrome 144+, tick remote debugging in chrome://inspect, then click Allow |
| Playwright MCP | Any MCP client (Claude Code, Codex, Cursor, Copilot and more) | Its own browser profile by default. Your Chrome with --extension (Playwright Extension) or --cdp-endpoint | Chosen tabs (one tab group per client) via the extension, approval skippable with a token; or whole browser via --cdp-endpoint |
| Playwright CLI | Claude Code, GitHub Copilot and other agents that run shell commands | Its own browser by default. Your Chrome with attach --extension=chrome or attach --cdp=chrome | Chosen tab via the Playwright Extension, or whole browser via --cdp |
| Chrome DevTools MCP | Any MCP client (Claude Code, Cursor, Copilot, Antigravity and more), plus a CLI | A new Ch

Top issues

Discussions

Latest release

v0.1.13 v0.1.13 2026-09-04
What changed

- Pin the MCP extra to mcp 2.1.1.
- Pin release build tooling to build 1.6.0 and setuptools 84.0.0.
- Preserve the Chrome permission and macOS accessibility reliability improvements from 0.1.12.

 Verification

- 251 unit tests passed with the MCP extra.
- pip-audit found no known vulnerabilities in the resolved environment.
- Wheel and source distribution built successfully.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON