chrome-automation

Automate Chrome browser actions via CDP with live visual feedback.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/jameingh/chrome-automation --skill chrome-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-automation
Source: https://github.com/jameingh/chrome-automation/tree/main
Command: npx skills add https://github.com/jameingh/chrome-automation --skill chrome-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, pnpm, rustup, cargo, git, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables automated control of a user's Chrome browser by connecting to it via the Chrome DevTools Protocol (CDP) and providing real-time visual feedback of automation actions.

Core Features & Use Cases

  • Connect to an existing Chrome instance via CDP and drive it programmatically
  • Preserve login state with a persistent automation profile across sessions
  • Automatic dependency installation and setup for a seamless onboarding
  • Reproducible browser automation workflows such as navigation, element interaction, form filling, and data collection
  • Use case: automate repetitive browser tasks for testing, data gathering, and routine workflows with live visual feedback

Quick Start

First-time setup is automatic: run the auto-install script for your platform; then start Chrome with a persistent profile; finally verify the connection by running a basic command.

For Mac: bash $HOME/Downloads/chrome-automation/scripts/auto-install-mac.sh For Windows: powershell -ExecutionPolicy Bypass -File "$HOME\Downloads\chrome-automation\scripts\auto-install-windows.ps1"

Start Chrome with persistent profile: Mac: bash $HOME/Downloads/chrome-automation/scripts/start-chrome-mac.sh Windows: powershell -ExecutionPolicy Bypass -File "$HOME\Downloads/chrome-automation\scripts/start-chrome-windows.ps1"

Test the connection: cd $HOME/Documents/agent-browser AGENT_BROWSER_HOME=$HOME/Documents/agent-browser ./bin/agent-browser --cdp 9222 get url

Frequently Asked Questions about chrome-automation

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

FAQPage Schema
Can I preserve my login state across Chrome automation sessions?

Yes, Chrome automation via CDP preserves login state by using a persistent automation profile across sessions. You start Chrome with a dedicated profile directory, which maintains your authenticated sessions and cookies for reproducible automated workflows.

What dependencies do I need to run CDP Chrome automation on macOS and Windows?

CDP Chrome automation requires a Bash-compatible shell, Node.js with pnpm, and a Rust toolchain including rustup and cargo. The skill provides automatic dependency installation scripts for both macOS and Windows to streamline environment setup.

How do I start Chrome with remote debugging for agent browser automation?

To start Chrome with remote debugging for agent browser automation, run the provided platform-specific startup script, such as start-chrome-mac.sh or start-chrome-windows.ps1. This launches Chrome with a persistent profile and opens the remote debugging port for CDP connections.

What repetitive browser tasks can I automate with CDP and a persistent profile?

With CDP and a persistent profile, you can automate repetitive browser tasks such as web navigation, element interaction, form filling, and data collection. These workflows are useful for automated testing, data gathering, and routine browser operations.

Why does Chrome CDP automation require a Rust toolchain and Node.js?

Chrome CDP automation requires a Rust toolchain to build the native agent that interfaces with the browser, and Node.js with pnpm to manage JavaScript dependencies and scripts. These tools work together to enable real-time visual feedback and reliable browser control.