faster-chrome-devtools-skill
faster-chrome-devtools-skill drives Chrome over the DevTools Protocol from a shell, with no MCP server, Puppeteer or Playwright.
- 173 ★ on the repository
- Last commit
Broad access
Why this level
- Connecting to your logged-in Chrome gives the agent access to open accounts and their data.
- The skill evaluates arbitrary JavaScript and any CDP method on pages.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/faster-chrome-devtools-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Connecting to your logged-in Chrome gives the agent access to open accounts and their data.
- The skill evaluates arbitrary JavaScript and any CDP method on pages.
This is third-party code. Review the repository files before installing.
What it does
The skill teaches an agent to work with a browser through a Node.js command line. The script connects to Chrome over WebSocket and can open and reuse tabs, read compact accessibility snapshots with stable element references, click and fill fields, and wait for text or a selector without blind sleeps. Screenshots are saved to a file as compressed JPEG or WebP and only the path enters the model context. You can read the console and failed network loads, evaluate JavaScript and call any CDP method with the `raw` command. A loopback-only background daemon keeps the connection open. A mode for the remote Cloudflare Browser Run browser hands login, MFA and CAPTCHA steps to a human.
Who it is for. Developers who give an agent UI checks, page debugging and data collection in an already logged-in Chrome.
Good fit when
- An agent checks layout and console errors after a frontend change.
- You collect data from a site where you are already signed in in your own Chrome.
- MCP screenshots bloat the context, while here the model gets only a file path.
- A scenario needs a CDP method that ready-made tools do not cover.
Not a fit when
- You need a full test framework with reports and parallel runs.
- The environment has no Node.js 22 or newer.
- The agent must not act in a Chrome profile with personal accounts open.
Example request
Launch a fresh anonymous Chrome on a throwaway profile, open https://news.ycombinator.com, take a screenshot and list the top five story titles.Limitations
Requires Node.js 22 or newer. To use your logged-in Chrome you enable remote debugging at `chrome://inspect/#remote-debugging`. Through that connection the agent sees and changes whatever you have open in the browser, including account sessions. No license is declared in the repository. The daemon stays in the background for up to 20 minutes after the last command, so stop it manually after working with personal accounts. Remote browsers need their address and token.
How to disable. Stop the daemon with `node skills/faster-chrome-devtools-skill/scripts/cdp.mjs stop` and turn off remote debugging in Chrome. Then remove the skill from the agents directory.
FAQ
How is it different from Chrome DevTools MCP?
There is no MCP server: the agent calls a script through the shell. The `raw` command reaches any CDP method and screenshots go to a file, not the context.
How do I stop the daemon?
Run `node skills/faster-chrome-devtools-skill/scripts/cdp.mjs stop`. If several daemons run, use `stop --id <id>` or `stop --all`.
How long does the connection live?
The daemon keeps the CDP connection for 20 minutes. This avoids repeated access prompts in Chrome.
Does it work with a cloud browser?
Yes, with Cloudflare Browser Run. Login, MFA, CAPTCHA and approvals can be handed to a human through Live View.
Which Node.js versions work?
Node.js 22 or newer. No packages to install: the script uses only built-in modules.
Discussion
No questions or reviews yet.
Related
SkillsA skill for Amp, Claude Code and Cursor: the agent drives your live Chrome with its open tabs and signed-in accounts through a single debugging toggle
A CLI, skill and MCP server for driving Chrome with short Puppeteer scripts, with tabs that keep state between calls
A Claude Code plugin that drives your Chrome over the DevTools Protocol: tabs, forms, page extraction and screenshots with no third-party dependencies
A CLI and skill for driving Chrome from an agent: page snapshots, clicks, console, network and audits in compact output
A Rust binary with no MCP server: an agent drives your open Chrome or Edge, and tabs are pinned with target labels.
The cdp skill: an agent drives your Chrome straight through the DevTools protocol, with 652 typed methods and no ready-made click or goto helpers
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| faster-chrome-devtools-skill (this card) | no | 173 | ||
| Chrome DevTools MCP | yes | not required | 55,199 | an MCP server with a fixed tool set; here a script calls any CDP method with no server |
| chrome-cdp | no | 3,289 | another CDP skill; this one adds a daemon, accessibility snapshots and a Cloudflare cloud browser |
README in short
The script is written entirely with Node.js built-ins, including a small WebSocket client. The daemon listens only on loopback, and its token and connection details sit in an owner-readable temporary file.