Logged In Google Chrome Skill

English

日本語

English

日本語

Appearance

Logged In Google ChromeManual Google login first. Playwright attachment second.

A practical workflow for Gmail and other Google apps using a dedicated Chrome profile and CDP.

Getting Started
Case Studies
Japanese Docs
GitHub
Logged In Google Chrome

Dedicated Chrome Profile

Keep your everyday Chrome profile separate from automation by using a custom user-data-dir.

Manual Google Login

Sign into Google in a regular Chrome window to avoid the automation security warning.

Playwright over CDP

Attach Playwright after login with connectOverCDP() and reuse the authenticated browser session.

Real Case Studies

Follow concrete examples that move from Google login to actual work products, not just browser setup.

Overview ​

This project packages a reliable login workflow for Google web apps:

  1. Launch normal Chrome with a dedicated profile directory
  2. Let the user log in manually
  3. Verify the CDP port
  4. Attach Playwright and automate the logged-in session

Who It Is For ​

  • Codex users who want a reusable Google-authenticated browser profile
  • Playwright users blocked by Google login warnings in automated browsers
  • Agent workflows that need Gmail, Google Account, Drive, or Docs access

The logged-in-google-chrome-skill-test report shows this skill being used to create and run a Google Apps Script project that generates a sample sales spreadsheet.

  • It reuses a manually authenticated Chrome profile

  • It attaches Playwright over CDP instead of logging in from an automated browser

  • It creates a script project, pastes code, runs it, approves access, and verifies the resulting spreadsheet

  • Read the Apps Script case study

Built for practical logged-in Chrome + Playwright workflows.

Copyright (c) 2026 Sunwood AI Labs