browser-use

Automate browser tasks with a persistent CLI daemon.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/guiledo/dotfiles --skill browser-use-guiledo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-use
Source: https://github.com/guiledo/dotfiles/tree/main/opencode/.config/opencode/skills/browser-use
Command: npx skills add https://github.com/guiledo/dotfiles --skill browser-use-guiledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repetitive browser tasks by maintaining a persistent browser daemon, reducing latency between actions and enabling stateful workflows across commands.

Core Features & Use Cases

  • Persistent browser daemon keeps the browser open across commands for rapid feedback.
  • Navigate, inspect, and interact with elements using open, state, click, type, and screenshot.
  • Supports profiles and CDP connections for authenticated or remote automation scenarios.

Quick Start

Open a URL with browser-use open https://example.com and then inspect the page with browser-use state to locate 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 maintain a persistent browser session for web scraping across multiple CLI commands?

To maintain a persistent browser session for web scraping, use a CLI daemon that keeps the browser open across commands, reducing latency and enabling stateful workflows for sequential navigation and interaction tasks.

Can I automate dynamic web interaction without launching a full browser environment each time?

Yes, you can automate dynamic web interaction by running a persistent background daemon that handles commands like open, click, and type, maintaining the browser state without restarting the environment for each action.

Does browser automation support authenticated sessions for repetitive navigation tasks?

Browser automation supports authenticated sessions by utilizing browser profiles and CDP connections, allowing you to interact with secured external sites and maintain login states during repetitive navigation tasks.

What is the best way to inspect and locate interactive elements on a page during headless browser automation?

The best way to inspect and locate interactive elements during headless browser automation is to use the state command after opening a URL, which reads the current page structure to identify actionable elements.

How do I capture visual proof of dynamic web scraping actions in a CLI environment?

To capture visual proof of dynamic web scraping actions, use the screenshot command within the CLI automation tool to generate an image of the current browser state after performing interactions like clicking or typing.

Why does my browser automation session close between sequential script executions?

Your browser automation session closes between executions if a persistent daemon is not utilized; keeping the daemon alive across commands is required to maintain the browser state and reduce latency between actions.