Logged-in Google Chrome (Playwright CDP attach)

What it does

This skill documents a safe workflow to launch a regular Chrome process using a dedicated user-data-dir, let the user complete manual Google account login, and then attach Playwright over the Chrome DevTools Protocol (CDP). It prevents Playwright-triggered login blocks and preserves an authenticated session that automation can reuse for Gmail, Google Account pages, or other Google web apps.

When to use it

Use this when an automation task needs an authenticated Google session (reading emails, managing Google Account pages, or interacting with Google web apps) and a Playwright-launched browser would trigger login restrictions. Also use when you need to persist a profile across runs or avoid tampering with the user's main Chrome profile.

What's included

• Scripts: references to PowerShell helper scripts (launch, close, check CDP port) described in the skill body.
• References: troubleshooting guidance for CDP connectivity and login blocks is mentioned.
• Instructions: step-by-step Quick Start (launch dedicated Chrome, wait for CDP, manual login if needed, attach via chromium.connectOverCDP), defaults (user-data-dir, port), rules and verification checks before automating.

Compatible agents

Best with agents or runtimes that can run Playwright or the JS REPL (Node.js + playwright/playwright-core). Works when the agent can run local scripts and attach to CDP endpoints.