sunwood-ai-labs/logged-in-google-chrome-skill

Use a normal Google Chrome window with a dedicated profile directory, log into Google manually, and then attach Playwright over CDP. This workflow avoids the “This browser or app may not be secure” block that can appear when Google login is attempted from a Playwright-launched browser.

🎬 Demo

https://x.com/haru_maki_ch/status/2031011134564872538

✨ Features

• Launch a dedicated Chrome profile that is safe to reuse for Gmail, Google Account, and other Google web apps
• Keep the user’s main Chrome profile separate from automation
• Attach Playwright after login by using chromium.connectOverCDP(...)
• Reuse the same logged-in Chrome session across multiple agent tasks
• Include helper scripts for launch, shutdown, and CDP port verification
• Ship bilingual project docs with VitePress in English and Japanese

🎯 Why This Exists

Google login often rejects automation-first browser sessions with a message similar to:

This browser or app may not be secure

This repository uses a more stable pattern:

1. Start regular Google Chrome with a dedicated --user-data-dir
2. Let the user log in manually
3. Attach Playwright over CDP only after login succeeds

📋 Requirements

• Windows
• Google Chrome installed
• Node.js 20+ recommended
• A workspace with playwright or playwright-core available when attaching from js_repl

🗂️ Repository Layout

logged-in-google-chrome-skill/
|- SKILL.md
|- README.md
|- README.ja.md
|- agents/
|  `- openai.yaml
|- references/
|  `- troubleshooting.md
|- scripts/
|  |- launch_logged_in_chrome.ps1
|  |- close_logged_in_chrome.ps1
|  `- check_cdp_port.ps1
`- docs/
   |- .vitepress/
   |- en/
   |- guide/
   |- ja/
   `- public/

🚀 Quick Start

1. Launch dedicated Chrome

powershell -ExecutionPolicy Bypass -File .\scripts\launch_logged_in_chrome.ps1

The launch script now waits until both of these are true before it reports success: