chrome-devtools-cli

Automates Chrome browser control via the DevTools Protocol from the command line.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill chrome-devtools-cli-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-devtools-cli
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/chrome-devtools-cli
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill chrome-devtools-cli-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Browser automation typically requires heavyweight runtimes like Puppeteer or MCP servers that spawn separate browser instances and consume large context. This Skill connects directly to your existing Chrome session via the DevTools Protocol, letting you navigate, click, fill forms, and extract data with simple one-shot CLI commands. ## Core Features & Use Cases - Direct Chrome Control: Navigate pages, click elements, fill inputs, press keys, and take screenshots against your running Chrome with its existing credentials and extensions. - Deterministic Multi-Page Targeting: Friendly target names like [target:green-dog] pin commands to specific tabs, avoiding index drift in multi-page workflows. - Structured Data Extraction: Evaluate JavaScript, capture accessibility tree snapshots, and get machine-readable output with --json for programmatic parsing. - Use Case: Automate a login flow by navigating to a page, filling username and password fields, clicking submit, waiting for the dashboard text to appear, and saving a confirmation screenshot. ## Quick Start Ask the agent to install chrome-devtools-cli, enable Chrome remote debugging, then navigate to a URL and take a screenshot of the page.

Frequently Asked Questions about chrome-devtools-cli

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

FAQPage Schema
How do I automate Chrome browser tasks from the command line?▼

Install chrome-devtools-cli via Homebrew or Cargo, enable remote debugging at chrome://inspect/#remote-debugging, then run commands like navigate, click, fill, and screenshot. The CLI auto-connects to your running Chrome instance without spawning a separate browser.

What is the difference between chrome-devtools-cli and MCP browser automation?▼

chrome-devtools-cli sends one command and returns one result with no MCP layer or large protocol payloads, minimizing context overhead. It also reuses your existing Chrome session with its credentials and extensions rather than launching a fresh browser.

Does chrome-devtools-cli work with my existing Chrome profile?▼

Yes, it connects to your running Chrome via the DevTools Protocol, preserving your session, cookies, and extensions. You can override the profile with CHROME_USER_DATA_DIR or select channels like beta or canary with CHROME_CHANNEL.

Why does chrome-devtools-cli fail to connect to Chrome?▼

Connection fails when Chrome is not running or remote debugging is not enabled at chrome://inspect/#remote-debugging. Verify the DevToolsActivePort file exists in the user data directory, or pass an explicit WebSocket endpoint with --ws-endpoint.

How do I target the correct tab in multi-page Chrome automation?▼

Capture the friendly target name like [target:green-dog] returned by the navigate command, then pass it with --target to all subsequent commands. Without it, commands default to page index 0, which can shift as Chrome reorders tabs.