domains / families / agent-tooling / browser-use

browser-use

combined

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages. Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.

When to use

• web testing
• form filling
• screenshots
• data extraction
• navigate websites
• interact with web pages
• fill forms
• extract information from web pages

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, t…

Skill page

Conflict

The two skills describe fundamentally different interfaces for the `browser-use` tool. The first (davidondrej) describes a Python-heredoc based CLI (`browser-use <<'PY'`) that uses a daemon, CDP directly, and specific helper functions like `new_tab()` and `page_info()`. It focuses on advanced CDP control, remote daemons, and specific local Chrome debugging workflows. The second (LeoYeAI) describes a command-line argument based CLI (`browser-use open <url>`, `browser-use click <index>`) that uses a state-based interaction model (getting indices from `state` and using them for clicks). These are mutually exclusive workflows; an agent following the first would fail if it tried to use the second's commands, and vice versa. Therefore, they must be combined to provide a complete picture of the available interfaces.