Why you'd want it
Browser Harness connects a coding agent to your running Chrome through the DevTools Protocol, so it can open pages, click, type, read and download with your existing logins. It installs as a CLI with a skill that teaches the browser workflow, and the agent writes missing helpers into its local workspace as it works while the core package stays protected. A browser-harness-mcp command exposes the same helpers as MCP tools for any MCP client.
Best for
- Logged-in web tasks from a coding agent
- Claude Code, Codex and Cursor
- MCP clients that need a real browser
Use it when
You want your coding agent to work in the browser where you are already signed in, instead of a fresh headless profile.
Skip it if
You do not want an agent acting in your real, logged-in browser profile: setup turns on Chrome remote debugging, and the agent acts as you on the sites you use. Optional local recordings save screenshots and action traces that may include sensitive page content.
Editor's note
Made by the browser-use team; cloud browsers are optional, and local Chrome needs no Browser Use API key.