browser-uselisted

# Browser Automation with browser-use CLI The `browser-use` command provides fast, persistent browser automation. A background daemon keeps the browser open across commands, giving ~50ms latency per call. ## Prerequisites ```bash browser-use doctor # Verify installation ``` For setup details, see https://github.com/browser-use/browser-use/blob/main/browser_use/skill_cli/README.md ## Core Workflow 1. **Navigate**: `browser-use open <url>` — launches headless browser and opens page 2. **Inspect**: `browser-use state` — returns clickable elements with indices 3. **Interact**: use indices from state (`browser-use click 5`, `browser-use input 3 "text"`) 4. **Verify**: `browser-use state` or `browser-use screenshot` to confirm 5. **Repeat**: browser stays open between commands If a command fails, run `browser-use close` first to clear any broken session, then retry. To use the user's existing Chrome (preserves logins/cookies): run `browser-use connect` first. To use a cloud browser instead: run `browser-use cloud connect` first. After either, commands work the same way. ### If `browser-use connect` fails When `browser-use connect` cannot find a running Chrome with remote debugging, prompt the user with two options: 1. **Use their real Chrome browser** — they need to enable remote debugging first: - Open `chrome://inspect/#remote-debugging` in Chrome, or relaunch Chrome with `--remote-debugging-port=9222` - Then retry `browser-use connect` 2. **Use managed Chromi