npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

chrome-cdp-launcher

v1.0.3

Published

CLI tool to launch isolated Chrome instances for CDP (Chrome DevTools Protocol) automation.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

gcoderbhgcoderbh

Keywords

chromecdpautomationplaywrightpuppeteerdevtools

Readme

🤖 Chrome CDP Isolated Profile Manager

This tool provides a seamless way to launch and manage isolated Google Chrome profiles with an exposed Chrome DevTools Protocol (CDP) port. It allows AI agents (like Antigravity or Playwright) to securely automate the browser without interfering with your primary, day-to-day Chrome data.

🚀 How to Use (Global CLI)

  1. Ensure you have installed the package globally (or use npm link for local development):
    npm i -g chrome-cdp-launcher
  2. Run the command from anywhere in your terminal:
    chrome-cdp-launcher
  3. First-time Setup:
    • The CLI will ask for permission to automatically locate your Chrome executable path based on your OS.
    • It will save this path in ~/.chrome-cdp-launcher-config.json for future use.
  4. Select a Profile to use (e.g., cdp-agent1) or create a new one. (Note: Each profile has completely isolated sessions, cookies, and browsing history. You can reuse the same profile to keep your social media or platform logins intact.)
  5. Confirm the debugging port (default is 9222). (Port 9222 is the standard port that AI systems and agents will automatically look for.)
  6. An isolated Chrome instance will launch. Keep this window open! (You can minimize it if you prefer).

🤖 How to Interact with the AI

Once the isolated Chrome window is open, AI agents running in your IDE (like Antigravity) will detect it instantly. You can then instruct the AI using natural language, for example:

  • "Go to Facebook and search for 'Apple'."
  • "Take a screenshot of this webpage."
  • "Analyze the structure of this page and tell me what buttons are clickable."
  • "Help me fill out this ad campaign form."

🛑 How to Stop

You can simply close the Chrome window manually like a normal browser, or go back to your terminal and press Ctrl+C to terminate the launcher process at any time.

⚙️ Technical Details (For Geeks)

  • Profile Data Storage: All isolated profiles are stored as black boxes in the following cross-platform directories:
    • macOS: ~/Library/Application Support/Chrome_CDP/
    • Windows: ~\AppData\Local\Chrome_CDP\
    • Linux: ~/.config/Chrome_CDP/
  • MCP Configuration: Ensure your agent's MCP Playwright configuration is pointing to http://127.0.0.1:9222.