项目文件夹
Shawn Pana
a8c4982693
install.md guided users through installing browser-harness and connecting to a browser, but assumed BROWSER_USE_API_KEY already existed — it never explained how to obtain a key. An agent following install.md in a headless environment (no local Chrome) dead-ends at the cloud-browser step. Add a "Get an API key" section that: - frames the key as optional (local browsers are free; the key is only for the recommended cloud browsers); - defaults to the agent challenge-response self-signup (POST /cloud/signup -> /verify -> bu_ key, free account, no human); - after success, tells the agent to explain what it did and handle ownership: if the user already has an account, use their key (ask, or fetch it via browser-harness in their own browser); if not and they want to keep the account, run /cloud/signup/claim and open the claim URL in their browser; - falls back to human key creation if the challenge fails. Mirrors docs.browser-use.com/llms.txt. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Browser Harness ♞
Connect an LLM directly to your real browser with a thin, editable CDP harness. For browser tasks where you need complete freedom.
One websocket to Chrome, nothing between. The agent writes what's missing during execution. The harness improves itself every run.
Try browser-harness in Browser Use Cloud or paste the setup prompt into your coding agent.
● agent: wants to upload a file
│
● agent-workspace/agent_helpers.py → helper missing
│
● agent writes it agent_helpers.py
│ + custom helper
✓ file uploaded
You will never use the browser again.
Setup prompt
Paste into Claude Code or Codex:
Set up https://github.com/browser-use/browser-harness for me.
Read `install.md` and follow the steps to install browser-harness and connect it to my browser.
The agent will open chrome://inspect/#remote-debugging. Tick the checkbox so the agent can connect to your browser:
Click Allow when the per-attach popup appears (Chrome 144+):
See agent-workspace/domain-skills/ for example tasks.
Free Browser Use Cloud browsers
Stealth, sub-agents, or headless deployment.
Browser Use Cloud free tier: 3 concurrent browsers, proxies, captcha solving, and more. 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).
Architecture (~1k lines across 4 core files)
install.md— first-time install and browser bootstrapSKILL.md— day-to-day usagesrc/browser_harness/— protected core packageagent-workspace/agent_helpers.py— helper code the agent editsagent-workspace/domain-skills/— reusable site-specific skills the agent edits
Contributing
PRs and improvements welcome. The best way to help: contribute a new domain skill under agent-workspace/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
agent-workspace/domain-skills/<site>/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.
Domain skills
Set BH_DOMAIN_SKILLS=1 to enable agent-workspace/domain-skills/ — community-contributed per-site playbooks goto_url surfaces by domain. Contribute via PR.
The Bitter Lesson of Agent Harnesses · Web Agents That Actually Learn