browser-use

Automate browser interactions via a persistent daemon with CDP connectivity.

Updated Dec 15, 2019

Search Tags:#automation #cloud #cdp #web-testing #browser #profiles #daemon

Ready to run

npx skills add https://github.com/matsuyoshi30/dotfiles --skill browser-use-matsuyoshi30

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-use
Source: https://github.com/matsuyoshi30/dotfiles/tree/main/.agents/skills/browser-use
Command: npx skills add https://github.com/matsuyoshi30/dotfiles --skill browser-use-matsuyoshi30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repetitive, manual browser tasks by providing a daemon-backed session that keeps a browser instance alive across commands, reducing latency and setup overhead.

Core Features & Use Cases

Daemon-backed browser with ~50ms call latency for rapid automation.
Real Chrome profile support via --profile, CDP connect to running Chrome, cloud browsers, and tunneling for remote access.
Persistent Python scripting session to maintain state across commands.
Rich CLI for navigation, state inspection, element interaction, data extraction, and cookies management.

Quick Start

Open a URL with browser-use and immediately run state to identify interactive elements.

Frequently Asked Questions about browser-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep a browser session alive for persistent browser automation?▼

Persistent browser automation is achieved by using a daemon-backed session that keeps the browser instance alive across commands, reducing latency and setup overhead for repetitive tasks.

Can I use my real Chrome profile for automated web testing?▼

Yes, automated web testing supports real Chrome profiles via the --profile flag, allowing you to maintain authenticated sessions and interact with websites using your existing browser state.

What's the best way to automate data extraction from websites with low latency?▼

The best way to automate low-latency data extraction is using a daemon-backed browser that provides approximately 50ms call latency, enabling rapid navigation, element interaction, and state inspection.

How do I connect to a running Chrome instance using CDP for workflow automation?▼

To connect to a running Chrome instance using CDP for workflow automation, you need CDP connectivity enabled, allowing the daemon to manage browser interactions and execute commands across the active session.

Does browser automation work with cloud browsers and tunneling for remote access?▼

Yes, browser automation works with cloud browsers and tunneling for remote access, allowing you to execute automated testing and workflow automation across remote environments and sessions.

Why does my automated browser testing have high latency between commands?▼

High latency in automated browser testing occurs when each command spins up a new browser instance; using a persistent daemon-backed session minimizes this overhead and maintains state across commands.