browser-uselisted

# Browser Use Direct browser control via CDP. For task-specific edits, use `agent-workspace/agent_helpers.py`. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md. ## When Not to Use A basic fetch of public information needs no browser. If a plain HTTP request can read it — a public page, an API, docs — use `curl` or your fetch tool, and leave the browser alone. Use browser-use when the task needs interaction (click, type, navigate), the user's logged-in session, JS rendering, or a bot-protected page. If a direct fetch fails or returns a shell page, then escalate to the browser. Domain skills are off by default. Set `BH_DOMAIN_SKILLS=1` to enable them; see the bottom section. **If `BH_DOMAIN_SKILLS=1` and the task is site-specific, read every file in the matching `$BH_AGENT_WORKSPACE/domain-skills/<site>/` directory before inventing an approach.** ## Usage ```bash browser-use <<'PY' print(page_info()) PY ``` - Invoke as `browser-use`. Use heredocs for multi-line commands. - Helpers are pre-imported. `run.py` calls `ensure_daemon()` before `exec`. - First navigation is `new_tab(url)`, not `goto_url(url)`. - The normal local flow attaches to the running Chrome/Chromium CDP endpoint. No browser ids or local profile selection. ## Local Chrome If the daemon cannot connect, run diagnostics: ```bash browser-use --doctor ``` If Chrome is not running at all, the harness launches it automatically and retries —