chrome-cdp-live-browser — Claude Code skill: drive your live Chrome
Hooks an AI agent into the Chrome you already have running, over the DevTools Protocol. Your tabs, logins and page state stay as they are.
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a claude-codeWhat chrome-cdp-live-browser does
This skill talks to a running Chrome through CDP. Tools that launch a fresh isolated browser start you from zero; here the agent works with the tabs already on screen, cookies and sessions included. Listing tabs, taking a screenshot, pulling the accessibility tree, grabbing full or selector-scoped HTML, running JavaScript, navigating, clicking an element or a coordinate pair, typing text, reading network resource timing — each is a separate call into scripts/cdp.mjs. Raw CDP commands can be passed through too.
One WebSocket daemon per tab keeps things quiet: Chrome's “Allow debugging” modal shows up once instead of on every call. There is no npm step, just Node.js 22+. The type command reaches into cross-origin iframes. Daemons shut down with stop, or stop <target> for a single tab.
Turn on remote debugging first: open chrome://inspect/#remote-debugging and flip the switch. Chrome, Chromium, Brave, Edge and Vivaldi are detected automatically on macOS, Linux and Windows; a non-standard install needs the DevToolsActivePort path in CDP_PORT_FILE. With debugging off, nothing runs — and open also triggers Chrome's own “Allow” prompt.
What it helps with
- read a page behind your own login
- fill in a form and submit it from the agent
- capture a screenshot of an open tab
- pull page data out with JavaScript
- click through pagination until the button is gone
Example prompts for the agent
- List the tabs I have open in Chrome
- Take a screenshot of the Gmail tab
- Run
evalon tab A1B2 to get the page title
How to install chrome-cdp-live-browser
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a claude-code2Manually: put the files in place
~/.claude/skills/chrome-cdp-live-browser/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chrome-cdp-live-browser/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a codex2Manually: put the files in place
.agents/skills/chrome-cdp-live-browser/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a cursor2Manually: put the files in place
.cursor/skills/chrome-cdp-live-browser/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills chrome-cdp-live-browser2Manually: put the files in place
.github/skills/chrome-cdp-live-browser/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/chrome-cdp-live-browserManually: put the files in place
.devin/skills/chrome-cdp-live-browser/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about chrome-cdp-live-browser
How do I install chrome-cdp-live-browser in Claude Code?
Run npx skills add reason-machines/trending-skills --skill chrome-cdp-live-browser -a claude-code. The skill lands at ~/.claude/skills/chrome-cdp-live-browser/SKILL.md.
What does chrome-cdp-live-browser do?
It links your agent to the Chrome session you are already using, over the Chrome DevTools Protocol. Tabs can be read and changed without losing your logins.
What does the skill need to work?
Node.js 22+ and the remote debugging switch turned on at chrome://inspect/#remote-debugging. For a non-standard browser install, point CDP_PORT_FILE at the DevToolsActivePort file.