browser-harnesslisted

# browser-harness Self-healing CDP automation framework. Connects directly to your running Chrome via a single WebSocket — agents get full browser freedom and write missing helpers during execution. ## When to Use (Decision Matrix) | Need | Use This | |------|----------| | QA testing / regression / health scores | agent-browser / browse | | Fast data extraction (no rendering) | Lightpanda | | Full browser interaction (MCP-native) | Playwright MCP | | **Real Chrome with your sessions/cookies/extensions** | **browser-harness** | | **Agent needs to learn and persist site-specific patterns** | **browser-harness** | | Local dev server testing | webapp-testing | Use browser-harness when: - You need the user's logged-in sessions (Gmail, LinkedIn, internal tools) - The task requires extensions or profiles that headless can't replicate - You want the agent to learn and improve across runs (self-healing) - You need stealth mode / captcha solving via Browser Use Cloud Do NOT use when: - You only need DOM extraction (Lightpanda is 9x faster) - You need structured QA reports with health scores (agent-browser) - You need MCP-native tool calls without heredocs (Playwright MCP) ## Setup Installed at: `~/Developer/browser-harness` (editable clone) Binary on PATH: `browser-harness` ### Connect to Chrome **Option A — Real profile (your running Chrome):** Navigate to `chrome://inspect/#remote-debugging` and tick the checkbox. Chrome 144+ shows a per-attach popup — click Allow. **Option