PlugWiki

browser-cdp Skill (zenstory-ai): Drive Logged-In Chrome

Lets Claude drive a copy of your Chrome that keeps your logins, so it can open pages, run page scripts and read data.

Installs
17.3K
on skills.sh
Stars
8.2K
on GitHub
Files
1
besides SKILL.md
Updated
Nov 2026
last repo commit

browser-cdp starts Chrome in remote-debugging mode on port 9222 and connects the agent-browser command-line tool to it. Claude can then open a URL, wait, read page text, take a snapshot, click, type and run JavaScript on the page. It works from a copy of your Chrome profile, so sites where you were logged in stay logged in.

It starts on phrases like "browser automation", "CDP", "复用登录态" or "extract token from browser". It needs Google Chrome you have already used, Node.js 20+ and agent-browser installed with npm install -g. If Chrome is already running, the setup script has to end its processes, and unsaved tabs or drafts can be lost, so the skill asks for your consent first. It is one of the 14 Oh Story skills.

Good for

  • Developers who need an agent to use sites where they are already logged in
  • People running the Oh Story chart-scan skills, which start Chrome through this one
  • Users comfortable with Node.js 20+ and installing a global npm package

Install browser-cdp

Claude Code

  1. 1

    Copy this prompt.

    Install the browser-cdp skill in Claude Code. Run this command:
    
    npx skills add https://github.com/zenstory-ai/oh-story-claudecode --skill browser-cdp
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Use this skill when you need to control a Chrome browser via CDP (Chrome DevTools Protocol) to reuse existing login sessions. Covers: launching Chrome in debug mode, opening URLs, waiting for page load, evaluating JavaScript, taking snapshots, and extracting auth tokens. Trigger phrases: browser automation, CDP, agent-browser, 浏览器操作, 操作浏览器, Chrome CDP, 复用登录态, extract token from browser.

Sections in SKILL.md

  1. 前置条件
  2. 启动流程(每次都按这个顺序)
  3. 启动脚本选项
  4. 常用操作
  5. 打开页面并等待加载
  6. 提取页面文本
  7. 提取 Auth Token
  8. 复杂 JS(含引号 / $ / 反引号)
  9. 页面交互(snapshot 拿元素引用)
  10. 停止 / 清理
  11. 长命令加超时
  12. 超时包装
  13. 已知限制
  14. 常见问题

Key facts

Installs on skills.sh
17,284 (Nov 2, 2026)
Last commit
2026-11-01

What it includes

  • Runs setup-cdp-chrome.js 9222 --detect-only to see if debug Chrome is ready

    Prints CDP_STATUS=ready or needs-setup, and whether a Chrome is running and how many processes. Changes nothing.

    Runs code · Detect state

  • Runs setup-cdp-chrome.js 9222 --yes when Chrome is not running

    Copies your Chrome profile into ~/chrome-debug-profile and launches Chrome with remote debugging on that copy.

    Runs code · Start debug Chrome

  • Dry-run first, tell you how many Chrome processes will end, then re-run with --yes

    Applies when Chrome is running, with --reset, or with --profile. If you refuse, the skill drops the automation.

    Runs code · Consent flow for ending Chrome

  • --detect-only, --yes, --reset, --profile <name>, --dry-run

    --reset clears ~/chrome-debug-profile before copying again. --profile picks another Chrome profile than Default.

    Delete · Script options

  • agent-browser --cdp 9222 open "<URL>", then wait

    Opens a page in the debug Chrome and waits for it to load.

    Runs code · agent-browser open and wait

  • Runs JavaScript on the page and returns text, links or stored values

    The skill shows reading page text and reading a token from localStorage or cookies. Complex scripts go in through base64 or stdin.

    Runs code · agent-browser eval

  • Lists interactive elements, then clicks or types by selector or @ref

    Used to get past a login page or to move through a site.

    Runs code · agent-browser snapshot, click, type

  • Close the debug window, or end only the debug instance after checking its PID

    The skill says never to end Chrome by executable name for manual cleanup.

    Runs code · Stop and clean up

From the official docs

Permissions

High risk

The skill hands an agent a Chrome that holds copies of your logins, and its setup can end your running Chrome and lose unsaved tabs. Use it only on accounts you own, save your tabs, and read the consent prompt before you agree.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can close your running Chrome

    With Chrome open, setup ends Chrome processes (on macOS, pkill -9 on Google Chrome). Unsaved tabs can be lost. Save your work and answer the consent question deliberately. github.com

  • Your logins are copied and used by the agent

    It copies your Chrome profile into ~/chrome-debug-profile and starts Chrome with --remote-debugging-port and --remote-allow-origins=*. Any page the agent opens uses those logins. github.com

  • It can read tokens from pages

    The skill's own example reads localStorage or cookies from the page. Only point it at accounts you own. github.com

  • --reset deletes a folder

    --reset clears ~/chrome-debug-profile before copying again. Its manual stop steps use kill -9 on a PID you have checked. github.com

  • Needs a global npm package

    It requires npm install -g agent-browser. Install only what you recognise. github.com

Technical details
Talks toAny site the agent opens in Chrome

Questions

What does browser-cdp do?

It lets the assistant control a Chrome window through the Chrome DevTools Protocol. It opens pages, reads text, runs JavaScript and clicks, and it keeps your existing logins by working on a copy of your Chrome profile.

How do I install browser-cdp?

Use the install box above. It also needs Google Chrome you have used before, Node.js 20+ and npm install -g agent-browser, as listed in SKILL.md. The README installs the whole Oh Story set with npx skills add zenstory-ai/oh-story-claudecode -y -g.

Will it close my Chrome?

It can. When Chrome is running, starting debug mode ends Chrome processes, and unsaved tabs or drafts can be lost. The skill does a dry run, tells you how many processes will end, and asks before it adds --yes.

Does it copy my logins?

Yes. The setup script copies your Chrome profile folder into ~/chrome-debug-profile and refreshes the cookie, saved-login and web-data files. Anything the assistant opens in that Chrome acts with those logins. --reset clears the copy.

Does it work in Claude Code, Codex and the Claude app?

The README names Claude Code, Codex CLI, Google Antigravity, OpenCode, ZCode, OpenClaw and Reasonix. It does not document the Claude app. The skill itself lists macOS, Linux and Windows (experimental).

Do I need an API key?

SKILL.md names none. The setup script reads the Windows folder variables PROGRAMFILES, PROGRAMFILES(X86) and LOCALAPPDATA to find Chrome.

Can it read my login tokens?

The skill has an "extract auth token" example that reads localStorage or cookies readable by JavaScript. Use it only on sites and accounts you own, and do not paste tokens into chats.

Is it safe to run?

It gives an agent control of a Chrome that holds copies of your logins, and the setup can end your running Chrome. Use it on accounts you own, tell the assistant which sites it may open, and save your tabs before you agree.

Information

updated Nov 2, 2026

Folder
skills/browser-cdp

zenstory-ai/oh-story-claudecodeskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5
  1. browser-cdp SKILL.md · github.com
  2. setup-cdp-chrome.js · github.com
  3. skills.sh listing · skills.sh
  4. zenstory-ai/oh-story-claudecode · github.com
  5. oh-story-claudecode README · github.com

Updated Nov 2, 2026.