Skip to content

Skills

Browser automation CLI built for AI agents. Break through anti-bot walls, hand off to humans across platforms when stuck. Parallel multi-task execution, independent…

Install

$git clone https://github.com/browser-act/skills

Install command taken from the project's README or registry entry. Always review code before running it.


What can BrowserAct be used for?

BrowserAct enables AI agents and teams to perform real-browser automation, web data extraction, and account-based workflows.

It helps agents get past anti-bot walls, hand off to humans across platforms when stuck, run parallel tasks without cross-contamination, and isolate multiple accounts in independent browsers, backed by stealth fingerprints, TLS rotation, residential proxies, CAPTCHA solving, and stable fingerprint-proxy setups for authenticated sessions.

Two usage modes are available: fully cloud-managed execution, or local browser control driven by your own agent workflow.

Use BrowserAct in the cloud

No agent setup required, with lower operating cost. Describe the website, filters, and fields you need. BrowserAct builds and tests a reusable scraping Bot in a real cloud browser, then runs it from the cloud. Build once. Run reliably. Improve continuously.

Start from BrowserAct Cloud →

Watch demo: Build a Web Scraper from One Prompt | BrowserAct →

Use BrowserAct locally with Skills

Use BrowserAct Skills when you want local browser control, local Chrome login-state reuse, or direct integration into your own AI agent workflow.

Your agent can load the BrowserAct Skill, discover browser state with get-skills, and run browser automation commands directly from your local environment.

Watch demo: BrowserAct: Give AI Agents a Real Browser →

Start from BrowserAct Skills →

Why BrowserAct

The browser an AI agent needs has to reach places standard tools can't, let a human seamlessly take over when the agent is stuck, keep parallel tasks from cross-contaminating, and be designed for LLM reasoning — not human-written scripts. A browser for agents must get four things right.

1. Break through blocks — three progressive layers

  1. Environment layer — stealth fingerprint spoofing, TLS rotation, proxy switching. The vast majority of blocks never trigger.
  2. Execution layer — solve-captcha auto-solves CAPTCHAs; stealth-extract pulls protected pages in one command.
  3. Human layer — remote-assist generates a live URL; the user takes over from any device, and the agent continues seamlessly when done.

2. Three browser modes — by real-world scenario

Mode Scenario Key trait
chrome Reuse local Chrome login state Profile import or CDP attach
stealth privacy mode Frictionless batch scraping without login Fresh fingerprint per session + proxy rotation, zero residue
stealth fixed identity Logged-in accounts · multi-browser parallel Stable fingerprint + stable IP, stable account identity, not flagged as bots

3. Zero-interference concurrency — every agent in its own lane

  • Cross-browser parallel — independent cookies, fingerprints, proxies. Sites cannot correlate them.
  • Same-browser multi-session — shared login state, independent execution, tasks don't block each other.
  • Privacy mode — fresh fingerprint and empty profile per session, zero residue when done.

4. Designed for agent reasoning — not human scripts

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…