browser-use

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.

86,455stars10,003forksUpdated 4/8/2026

Developer Tools #web-testing #data-extraction #form-filling #browser-automation #javascript

Security Assessment

Safe(100/100)

Security Score100/100

About browser-use

The 'browser-use' skill provides powerful browser automation tools for testing, form filling, screenshots, and web scraping. It simplifies and accelerates browser interactions by automating repetitive tasks like navigating websites, filling out forms, and extracting data. By using a background daemon to keep the browser running, this skill minimizes latency, offering near-instant responses with ~50ms per call. It is ideal for developers and testers who need to automate web-based workflows for testing or data extraction across multiple pages or forms.

FAQ

How do I set up the browser-use skill?

To set up 'browser-use', verify the installation by running 'browser-use doctor'. For full setup instructions, refer to the README at https://github.com/browser-use/browser-use/blob/main/browser_use/skill_cli/README.md.

Can I use my existing Chrome browser with this skill?

Yes, you can use your existing Chrome browser by running 'browser-use connect'. This will preserve your logins and cookies.

How do I take a screenshot using this skill?

To take a screenshot, use the 'browser-use screenshot' command. Optionally, you can provide a file path to save the screenshot, or use '--full' for a full-page capture.

What browsers are supported?

By default, 'browser-use' uses headless Chromium. You can also connect to your Chrome browser or use a cloud browser by running 'browser-use connect' or 'browser-use cloud connect', respectively.

What are the limitations of using this skill?

This skill is designed for browser automation and may not support complex interactions outside the web context, like managing non-web applications or environments that don't have a browser interface.