
from logged-in-google-chrome-skill20
Start a separate Chrome profile, perform manual Google login, and attach Playwright over CDP so automation can interact with Google services without login block
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.
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.
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.
This skill has not been reviewed by our automated audit pipeline yet.