Browser CDP
Drive Chrome over CDP to reuse existing login sessions for automation
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 17, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 5667f33
The bundled setup-cdp-chrome.js ran cleanly in --detect-only and --dry-run, correctly detecting the user's live Chrome and refusing to kill it without --yes (exits code 3 NEEDS_CONSENT in non-TTY, which is the right safety default). It copies the Chrome profile locally to reuse login state and stays on-machine with no network exfiltration. The task delta is unmeasured: the real path needs a global agent-browser install (not present) and would kill the user's running Chrome, so the automation itself could not be safely exercised. The skill body is almost entirely in Chinese.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 4/5
What Browser CDP does
A runbook plus setup script for controlling Chrome through the DevTools Protocol so automation reuses your already-logged-in session: launch Chrome in debug mode, open URLs, run JavaScript, take snapshots, and extract auth tokens via the agent-browser CLI. Triggers on browser automation, CDP, agent-browser, or extract token from browser. Requires a global agent-browser install and will restart your Chrome.
How to install Browser CDP
git clone https://github.com/worldwonderer/oh-story-claudecode
mkdir -p ~/.claude/skills
cd oh-story-claudecode && cp -r skills/browser-cdp ~/.claude/skills/browser-cdp
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Browser CDP
-
/browser-cdpDrive Chrome over CDP to reuse existing login sessions for automation
It also activates on plain-language prompts like these:
-
automate my browser but keep me logged into my accounts -
extract my auth token from my already-logged-in Chrome session -
control Chrome over CDP without making me log in again
Frequently asked questions
- Is the Browser CDP skill free?
- Yes. The skill itself is free from worldwonderer/oh-story-claudecode. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Browser CDP work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 17, 2026. Verdict: Works with setup. The bundled setup-cdp-chrome.js ran cleanly in --detect-only and --dry-run, correctly detecting the user's live Chrome and refusing to kill it without --yes (exits code 3 NEEDS_CONSENT in non-TTY, which is the right safety default). It copies the Chrome profile locally to reuse login state and stays on-machine with no network exfiltration. The task delta is unmeasured: the real path needs a global agent-browser install (not present) and would kill the user's running Chrome, so the automation itself could not be safely exercised. The skill body is almost entirely in Chinese.
- What is the Browser CDP SkillProof Score?
- 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
- How do I install Browser CDP?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Browser CDP with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.