logged-in-google-chrome

Launch Chrome with a dedicated profile for manual Google login, then attach Playwright via CDP.

20|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Sunwood-ai-labs/logged-in-google-chrome-skill --skill logged-in-google-chrome-sunwood-ai-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logged-in-google-chrome
Source: https://github.com/Sunwood-ai-labs/logged-in-google-chrome-skill/tree/main
Command: npx skills add https://github.com/Sunwood-ai-labs/logged-in-google-chrome-skill --skill logged-in-google-chrome-sunwood-ai-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables users to log into Google services manually in a dedicated Chrome profile and then attach Playwright over CDP to automate with an already authenticated session.

Core Features & Use Cases

  • Manual Google Login Workflow: Launch a Chrome browser with a dedicated profile and perform login manually to bypass security warnings.
  • Attach Playwright over CDP: Connect to the browser post-login using connectOverCDP() for automation tasks.
  • Use Case: Automate Gmail, Google Drive, and Apps Script activities without triggering login security blocks or re-authenticating repeatedly.

Quick Start

Run the PowerShell script to launch Chrome with a dedicated profile, then manually log into Google, verify the CDP port, and connect Playwright for automation.

Frequently Asked Questions about logged-in-google-chrome

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

FAQPage Schema
How do I automate Google Drive and Gmail with Playwright without triggering login security blocks?

To automate Google Drive and Gmail with Playwright without triggering security blocks, you manually log into a dedicated Chrome profile first. Then, you attach Playwright via CDP to reuse the authenticated session for stable automation.

Why does Playwright fail to automate Google web apps after a standard login?

Playwright fails to automate Google web apps after a standard login because Google detects automated browsers and blocks them. Using CDP to attach to a manually logged-in Chrome profile bypasses these security restrictions.

Can I connect Playwright over CDP to an existing Chrome session?

Yes, you can connect Playwright over CDP to an existing Chrome session. By launching Chrome with a dedicated user profile and verifying the CDP port, you attach Playwright to automate Google web apps using an already authenticated session.

What is the best way to maintain a stable Google login session for web automation?

The best way to maintain a stable Google login session for web automation is to separate user profiles. You launch a dedicated Chrome profile, log in manually, and then attach Playwright over CDP to ensure safe and stable automated control.

Does attaching Playwright over CDP keep my Google account secure during automation?

Attaching Playwright over CDP keeps your Google account secure by separating user profiles and only attaching automation after manual login completion. This prevents automated login attempts that trigger security warnings.

What do I need to set up before automating Google Apps Script with Playwright?

Before automating Google Apps Script with Playwright, you need to run a script to launch Chrome with a dedicated profile. After manually logging into Google, verify the CDP port to connect Playwright for automation.