agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
npx skills add melandlabs/openloomi --skill agent-browser --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Browser Automation with agent-browser ## Installation ### Global Installation (recommended) Installs the native Rust binary for maximum performance: ```bash npm install -g agent-browser agent-browser install # Download Chromium ``` This is the fastest option -- commands run through the native Rust CLI directly with sub-millisecond parsing overhead. ### Quick Start (no install) Run directly with `npx` if you want to try it without installing globally: ```bash npx agent-browser install # Download Chromium (first time only) npx agent-browser open example.com ``` > **Note:** `npx` routes through Node.js before reaching the Rust CLI, so it is noticeably slower than a global install. For regular use, install globally. ### Homebrew (macOS) ```bash brew install agent-browser agent-browser install # Download Chromium ``` ### Linux Dependencies On Linux, install system dependencies: ```bash agent-browser install --with-deps # or manually: npx playwright install-deps chromium ``` ## Core Workflow Every browser automation follows this pattern: 1. **Navigate**: `agent-browser open <url>` 2. **Snapshot**: `agent-browser snapshot -i` (get element refs like `@e1`, `@e2`) 3. **Interact**: Use ref
- Installation
- Global Installation (recommended)
- Quick Start (no install)
- Homebrew (macOS)
- Linux Dependencies
- Core Workflow
- Command Chaining
- Essential Commands
- Common Patterns
- Form Submission
- Authentication with State Persistence
- Session Persistence
- Data Extraction
- Parallel Sessions
npm install -g agent-browser agent-browser install # Download Chromium npx agent-browser install # Download Chromium (first time only) npx agent-browser open example.com brew install agent-browser agent-browser install --with-deps or manually: npx playwright install-deps chromium agent-browser open https://example.com/form agent-browser snapshot -i agent-browser fill @e1 "user@example.com"
What does the agent-browser skill do?
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
How do I install it?
Run `npx skills add melandlabs/openloomi --skill agent-browser --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From melandlabs/openloomi, a repository with 764 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.