managed-chrome-cdp

Prewarm Chrome CDP sessions with a persisted user profile and reusable cookies.

3|Updated Jan 14, 2014

Search Tags:#browser-automation #puppeteer-core #chrome-cdp #headless-chrome #prewarm #cookie-management

Ready to run

npx skills add https://github.com/prateek/dotfiles --skill managed-chrome-cdp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: managed-chrome-cdp
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/managed-chrome-cdp
Command: npx skills add https://github.com/prateek/dotfiles --skill managed-chrome-cdp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander, puppeteer-core, and includes scripts (resource) components.

What problem does it solve?

Reduce the time and flakiness of Chrome DevTools Protocol automation by starting sessions with a prewarmed profile and reusable cookies, so automation can run without repeated login and policy initialization.

Core Features & Use Cases

Prewarm Chrome CDP sessions using the included browser-tools.ts script.
Reuse login cookies by persisting a user-data-dir profile and optionally caching policy state.
Provide recovery options for failed launches, with headless and headed modes, and easy profile management.
Use Case: automation pipelines that require consistent CDP connectivity and cookie state across runs.

Quick Start

Run bun ~/.agents/skills/managed-chrome-cdp/scripts/browser-tools.ts start --headless --port 9333 to launch a headless Chrome CDP session with a reusable profile.

Frequently Asked Questions about managed-chrome-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reuse cookies in Chrome DevTools Protocol automation to avoid repeated logins?▼

You can reuse cookies in Chrome DevTools Protocol automation by persisting a user-data-dir profile with a prewarmed session, allowing automation to run without repeated login and policy initialization.

What is the best way to prewarm a headless Chrome CDP session for enterprise automation pipelines?▼

The best way to prewarm a headless Chrome CDP session is to use a dedicated browser-tools script that launches Chrome with a reusable user-data-dir profile, reducing time and flakiness for enterprise automation pipelines.

Does puppeteer-core work with a prewarmed Chrome CDP profile to speed up web workflows?▼

Yes, puppeteer-core works with a prewarmed Chrome CDP profile by connecting to a persistent user-data-dir, which speeds up web workflows and ensures consistent CDP connectivity across runs.

How do I launch a headless Chrome CDP session on a specific port using a reusable profile?▼

You launch a headless Chrome CDP session on a specific port by running the browser-tools script with start, headless, and port flags, applying a reusable profile for reliable CDP access.

Why does Chrome CDP automation fail on repeated logins and how can I fix the flakiness?▼

Chrome CDP automation fails on repeated logins due to session initialization overhead and policy resets, which you can fix by prewarming a user profile and reusing cookies to stabilize the automation.

Can I recover a failed headless Chrome launch when using a persisted user-data-dir profile?▼

Yes, you can recover a failed headless Chrome launch using the provided recovery options for failed launches, supporting both headless and headed modes with easy profile management.