logged-in-google-chrome

Launch a dedicated Chrome profile and attach Playwright over CDP after manual login.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/i0switch/yoyaku-tosho --skill logged-in-google-chrome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logged-in-google-chrome
Source: https://github.com/i0switch/yoyaku-tosho/tree/main/.github/skills/logged-in-google-chrome-skill
Command: npx skills add https://github.com/i0switch/yoyaku-tosho --skill logged-in-google-chrome

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Launch a dedicated Chrome profile, allow manual Google login, and then attach Playwright over CDP to reuse the authenticated session for automation tasks, avoiding login prompts and security blocks.

Core Features & Use Cases

  • Separate Chrome profile for automation to keep daily browsing safe and isolated.
  • Manually log into Google once, then attach Playwright to continue automation against the authenticated session.
  • Reuse the authenticated browser across multiple tasks and agents, reducing repeated sign-ins and setup.

Quick Start

Start Chrome with a dedicated user-data-dir using the provided PowerShell script, complete Google login, verify the CDP port, and attach Playwright from your workspace with connectOverCDP.

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 reuse a manually logged-in Chrome session with Playwright?

To reuse a manually logged-in Chrome session with Playwright, start Chrome with a dedicated user-data-dir, complete your Google login manually, verify the CDP port is reachable, and then attach Playwright using connectOverCDP to continue automation against the authenticated session.

How do I start Chrome with a dedicated user-data-dir for session reuse?

You start Chrome with a dedicated user-data-dir for session reuse by running the provided PowerShell script, which launches an isolated Chrome profile. This keeps daily browsing safe and allows manual Google login before attaching Playwright over CDP.

Do I need a separate Chrome profile to automate Google apps with Playwright?

Yes, you need a separate Chrome profile for automating Google apps with Playwright to keep daily browsing isolated and safe. This dedicated user-data-dir ensures manual Google login persists without triggering security blocks in your automated workflows.

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

Yes, you can connect Playwright over CDP to an existing Chrome session by verifying the CDP port is reachable after manually logging into your dedicated Chrome profile. This allows agent workflows to interact with authenticated Google apps without repeated sign-ins.

Why does Playwright automation get blocked by Google login prompts?

Playwright automation gets blocked by Google login prompts because automated browsers lack prior authentication and use default profiles. Reusing a manually logged-in Chrome session over CDP avoids these security blocks by leveraging an already authenticated dedicated profile.