browser-harness
Browser Harness connects coding agents to Chrome through the DevTools Protocol and exposes browser operations through a CLI or MCP. Its typical use is work that benefits from an existing browser session, while its local workspace lets an agent retain task-specific helper code. That retained code should be reviewed as executable automation; it does not establish that a model has trained itself or learned every similar website.
We installed browser-harness 0.1.13 with its MCP extra and tested an isolated headless Chrome 156 profile against a synthetic local page. Discovery returned 23 tools. Input, coordinate clicking, a normal file upload, localStorage after reload, switching between owned tabs and screenshot capture succeeded. The saved result text and visible filename were checked as outcomes rather than assuming that a returned tool call meant the action succeeded.
A missing-selector call returned an error field inside JSON content while the outer MCP isError flag remained false; the next page inspection still worked. Hosts therefore need to parse the tool's content and define their own completion checks. This test did not cover personal logins, authorization dialogs, real-site tasks, autonomous model planning or comparative performance. Our loopback proxy setup also needed adjustment before the CDP connection worked.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-09
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 5
- Latest release
- v0.1.13 (2026-09-04)
- Open issues
- 454
- Recent issues with at least one comment
- 0/5
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Who it fits
- A coding agent needs browser actions in a deliberately chosen session or profile.
- You can review reusable helpers and implement visible outcome checks and error recovery.
- Your main requirement is deterministic CI testing of your own application with a clean browser.
- You expect the browser connection itself to enforce granular business permissions.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!