agent-browser

Automate Chrome/Chromium browser tasks via CDP using a Rust CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MrWest3/west-command-center --skill agent-browser-mrwest3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/MrWest3/west-command-center/tree/main/templates/analyst/.claude/skills/agent-browser
Command: npx skills add https://github.com/MrWest3/west-command-center --skill agent-browser-mrwest3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser automation for AI agents is often clunky or slow when bridging tasks that require navigating websites, filling forms, clicking controls, taking screenshots, and extracting data. This skill provides a fast, self-contained CLI to orchestrate browser actions directly via Chrome/Chromium using CDP, enabling reliable automation without additional dependencies.

Core Features & Use Cases

  • Native Rust CLI with CDP-based browser control (no Playwright or Puppeteer dependency)
  • Session management, authentication vault, and state persistence for long-running tasks
  • Open websites, fill forms, click elements, take screenshots, extract data, and perform lightweight testing or QA
  • Support for automating browser tasks across AI agents and workflows, including Electron app automation and QA scenarios
  • Lightweight, scriptable, and easily extensible for custom automation pipelines

Quick Start

Install agent-browser and start using it to automate a browser task such as opening a website and filling a form.

Frequently Asked Questions about agent-browser

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

FAQPage Schema
How do I automate browser tasks for AI agents without using Puppeteer or Playwright?

Browser automation for AI agents is handled by controlling Chrome or Chromium directly via CDP using a native Rust CLI, bypassing Puppeteer or Playwright entirely. This enables reliable execution of actions like opening websites, filling forms, and extracting data without additional dependencies.

Can I persist authenticated sessions and secure credentials for web interaction automation?

Authenticated sessions and credentials can be persisted using optional session management and vault components during web interaction automation. This allows you to maintain state and secure logins across long-running browser tasks and workflows.

How do I fill forms and take screenshots during web interaction testing via CDP?

Filling forms and taking screenshots during web interaction testing is achieved by sending CDP commands through the Rust CLI to control Chrome. You can script these actions sequentially to automate QA workflows, extract data, and capture page states.

What is CDP-based browser automation and when do I need it for CLI testing?

CDP-based browser automation is the process of controlling Chrome instances directly through the Chrome DevTools Protocol. You need it for CLI testing when executing lightweight QA, extracting web data, or automating Electron apps without the overhead of high-level framework dependencies.

Does browser automation via CDP support Electron app testing and custom automation pipelines?

Browser automation via CDP supports Electron app testing and custom automation pipelines by leveraging Chrome's underlying protocol. The Rust CLI is lightweight and scriptable, allowing you to easily extend browser actions into specialized workflows.

Why does my AI agent's browser automation fail to maintain state across long-running tasks?

Browser automation fails to maintain state across long-running tasks if session management and state persistence components are not configured. Applying the optional vault and session features ensures authenticated state is secured and carried over between actions.