Browser Harness
PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and has been in the index since 28 Jun 2026. How this is checked
Browser Harness is an open-source framework for building self-healing browser agents directly on the Chrome DevTools Protocol (CDP). It allows agents to edit their own helpers mid-task and can run locally or in the cloud. Designed for developers building robust browser automation solutions.
Inferred · not functionally tested
Overview
5 featuresPurpose: Enabling developers to build robust, self-healing browser automation agents using a flexible open-source harness.
Inferred · not functionally tested
Audience: automation developers
Inferred · not functionally tested
Functions: browser_automation, agents
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: WEB · deployment: browser
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: browser-harness.com · github.com. These links do not verify the individual claims.
Browser Harness is a Frameworks & SDKs project. Inferred · not functionally tested: Enabling developers to build robust, self-healing browser automation agents using a flexible open-source harness. Inferred · not functionally tested: Browser Harness is an open-source project aimed at automation developers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the web.
Behind Browser Harness is Browser Use, and it first shipped in 2026. The project is developed in the open on GitHub with 15.4k stars and 424 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include self-healing agents, CDP integration, and open source. Inferred · not functionally tested: Catalogued interfaces include a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Self-healing agents
- CDP integration
- Open source
- Local or cloud execution
- Agent helper editing
Topics: Inferred · not functionally tested
Built with & integrations
- Next.js
- x-nextjs-prerender header · /_next/static/ in the HTML · __next_f in the HTML
- Vercel
- x-vercel-id header · x-vercel-cache header
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about Browser Harness
- What is Browser Harness?
- Inferred · not functionally tested: Enabling developers to build robust, self-healing browser automation agents using a flexible open-source harness. It is catalogued under Frameworks & SDKs on PulseGate.
- Who is Browser Harness for?
- Inferred · not functionally tested: Browser Harness is an open-source project built for automation developers.
- Is Browser Harness free?
- Basis unknown · not verified: Yes — Browser Harness is open source under the MIT license and free to use.
- What platforms does Browser Harness run on?
- Basis unknown · not verified: Browser Harness runs on the web.
- Is Browser Harness still maintained?
- PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 424 commits in the last 90 days.
- What are alternatives to Browser Harness?
- Similar projects tracked by PulseGate include Browser-Harness, browser-harness, and HarnessRouter.Browser-Harnessbrowser-harnessHarnessRouter
- Who makes Browser Harness?
- Browser Harness is developed by Browser Use.
- When did Browser Harness launch?
- Browser Harness first shipped in 2026.
Similar projects
Closest matches by what these projects do