Browser CDP connects an agent to Google Chrome through the Chrome DevTools Protocol so it can work with sites you are already signed in to. A bundled Node script checks whether a debug Chrome is already listening, and if not, copies your Chrome profile into a separate debug profile and launches Chrome on a debugging port. The agent then uses the agent-browser command line tool to open pages, wait, evaluate JavaScript, take snapshots, click, type and extract text or tokens.
In the Oh Story writing toolkit it supplies the logged-in browser session that the ranking scan skills use to read web novel charts. The skill asks for your consent before it closes any running Chrome.
What You Get
- A debug Chrome on port 9222 (or another port) that carries your copied login state
- agent-browser commands to open pages, wait, evaluate JavaScript, take snapshots, click and type
- A consent flow with dry run, exit codes and a refusal to kill Chrome without agreement
- Timeout wrappers for slow page loads and batch scraping, plus a troubleshooting table
Common Use Cases
- Reading pages that need a login without handling passwords
- Scraping ranking pages for the Oh Story scan skills
- Extracting a page’s text or an auth token from local storage
- Automating clicks and typing in a signed-in browser
What Makes It Unique
It reuses the login state of your own Chrome profile, so the agent never asks for credentials. Its setup script is built around safety checks: a detect-only mode, an explicit consent step before closing Chrome, a hard stop when the debug port is held by another process, and identity checks that the port answers from the instance it launched.
Under The Hood
The skill has one bundled script, a Node program that detects Chrome, may stop running Chrome processes (only with your consent), copies your Chrome profile, including cookies and saved login files, into a separate debug profile folder in your home directory, and starts Chrome with remote debugging on a local port. The instructions then tell the agent to run the agent-browser command line tool, which you install with npm, to open web pages, evaluate JavaScript in them and read page text or tokens from local storage. It also names kill commands for cleanup of the debug instance only. The copied profile keeps your logins on disk until you delete it, and any agent able to reach the debug port can act as you in that browser.