Show HN: Self-healing browser harness via direct CDP

The simplest, thinnest, self-healing harness that gives LLM complete freedom to complete any browser task. Built directly on CDP. The agent writes what's missing, mid-task. No framework, no recipes, no rails. One websocket to Chrome, nothing between. ● agent: wants to upload a file │ ● helpers.py → upload_file() missing │ ● agent edits the harness and writes it helpers.py 192 → 199 lines │ + upload_file() ✓ file uploaded You will never use the browser again. Paste into Claude Code or Codex: Set up https://github.com/browser-use/browser-harness for me. Read `install.md` first to install and connect this repo to my real browser. Then read `SKILL.md` for normal usage. Always read `helpers.py` because that is where the functions are. When you open a setup or verification tab, activate it so I can see the active browser tab. After it is installed, open this repository in my browser and, if I am logged in to GitHub, ask me whether you should star it for me as a quick demo that the interaction works — only click the star if I say yes. If I am not logged in, just go to browser-use.com. When this page appears, tick the checkbox so the agent can connect to your browser: See domain-skills/ for example tasks. Useful for sub-agents or deployment. Free tier: 3 concurrent browsers, no card required. - Grab a key at cloud.browser-use.com/new-api-key - Or let the agent sign up itself via docs.browser-use.com/llms.txt (setup flow + challenge context included). install.md — first-time install and browser bootstrapSKILL.md — day-to-day usagerun.py (~36 lines) — runs plain Python with helpers preloadedhelpers.py (~195 lines) — starting tool calls; the agent edits theseadmin.py +daemon.py (~361 lines) — daemon bootstrap plus the CDP websocket and socket bridge PRs and improvements welcome. The best way to help: contribute a new domain skill under domain-skills/ for a site or task you use often (LinkedIn outreach, ordering on Amazon, filing expenses, etc.). Each skill teaches the agent the selectors, flows, and edge cases it would otherwise have to rediscover. - Skills are written by the harness, not by you. Just run your task with the agent — when it figures something non-obvious out, it files the skill itself (see SKILL.md). Please don't hand-author skill files; agent-generated ones reflect what actually works in the browser. - Open a PR with the generated domain-skills// folder — small and focused is great. - Bug fixes, docs tweaks, and helper improvements are equally welcome. - Browse existing skills ( github/ ,linkedin/ ,amazon/ , ...) to see the shape. If you're not sure where to start, open an issue and we'll point you somewhere useful.