logged-in-google-chrome

Category: Development & Coding | Uploader: Sunwood-ai-labs | Downloads: 0 | Version: v1.0（Latest）

Launch and reuse a Google Chrome session that is logged into a Google account by using a dedicated user-data-dir and attaching Playwright over CDP after manual login. Use when Codex needs to work with Gmail, Google Account pages, or other Google web apps without triggering the "browser or app may not be secure" login block from a Playwright-launched browser.

Changelog: Source: GitHub https://github.com/Sunwood-ai-labs/logged-in-google-chrome-skill

Directory Structure

Current level: Root

📁 .github/
- 📁 workflows/
  - 📄 deploy-docs.yml 1.1 KB
📁 agents/
- 📄 openai.yaml 276 B
📁 docs/
- 📁 .vitepress/
  - 📁 theme/
    
    📄 custom.css 631 B
    
    📄 index.ts 97 B
  - 📄 config.ts 5.0 KB
- 📁 en/
  - 📁 guide/
    
    📄 architecture.md 1.2 KB
    
    📄 case-studies.md 149 B
    
    📄 getting-started.md 143 B
    
    📄 release-notes.md 181 B
    
    📄 troubleshooting.md 159 B
    
    📄 usage.md 119 B
  - 📄 index.md 341 B
- 📁 guide/
  - 📄 architecture.md 2.9 KB
  - 📄 case-studies.md 2.6 KB
  - 📄 getting-started.md 1.4 KB
  - 📄 release-notes.md 2.1 KB
  - 📄 troubleshooting.md 1.3 KB
  - 📄 usage.md 898 B
- 📁 ja/
  - 📁 guide/
    
    📄 architecture.md 3.5 KB
    
    📄 case-studies.md 3.1 KB
    
    📄 getting-started.md 1.4 KB
    
    📄 release-notes.md 2.6 KB
    
    📄 troubleshooting.md 1.6 KB
    
    📄 usage.md 882 B
  - 📄 index.md 2.9 KB
- 📁 public/
  - 📄 favicon.svg 460 B
  - 📄 logged-in-google-chrome-boundaries-and-rules-ja.drawio 2.5 KB
  - 📄 logged-in-google-chrome-boundaries-and-rules-ja.svg 191.1 KB
  - 📄 logged-in-google-chrome-boundaries-and-rules.drawio 2.5 KB
  - 📄 logged-in-google-chrome-boundaries-and-rules.svg 199.3 KB
  - 📄 logged-in-google-chrome-repository-structure-ja.drawio 2.7 KB
  - 📄 logged-in-google-chrome-repository-structure-ja.svg 237.9 KB
  - 📄 logged-in-google-chrome-repository-structure.drawio 2.7 KB
  - 📄 logged-in-google-chrome-repository-structure.svg 237.6 KB
  - 📄 logged-in-google-chrome-runtime-workflow-ja.drawio 5.1 KB
  - 📄 logged-in-google-chrome-runtime-workflow-ja.svg 289.1 KB
  - 📄 logged-in-google-chrome-runtime-workflow.drawio 5.0 KB
  - 📄 logged-in-google-chrome-runtime-workflow.svg 297.3 KB
  - 📄 logo.svg 746 B
  - 📄 ogp.svg 2.5 KB
  - 📄 release-notes-header.svg 4.0 KB
- 📄 index.md 2.5 KB
- 📄 package-lock.json 85.9 KB
- 📄 package.json 268 B
📁 references/
- 📄 troubleshooting.md 1.9 KB
📁 scripts/
- 📄 check_cdp_port.ps1 436 B
- 📄 close_logged_in_chrome.ps1 667 B
- 📄 launch_logged_in_chrome.ps1 2.6 KB
📄 .gitignore 86 B
📄 README.ja.md 8.8 KB
📄 README.md 8.1 KB
📄 SKILL.md 3.5 KB

SKILL.md

---
name: logged-in-google-chrome
description: Launch and reuse a Google Chrome session that is logged into a Google account by using a dedicated user-data-dir and attaching Playwright over CDP after manual login. Use when Codex needs to work with Gmail, Google Account pages, or other Google web apps without triggering the "browser or app may not be secure" login block from a Playwright-launched browser.
---

# Logged In Google Chrome

Use a dedicated Chrome user-data-dir and attach Playwright only after Chrome is already running.

## Quick Start

1. Run [scripts/launch_logged_in_chrome.ps1](./scripts/launch_logged_in_chrome.ps1) to start normal Chrome with a dedicated profile folder and a CDP port.
   The script now waits for the dedicated-profile Chrome process and the CDP endpoint before it reports success.
2. Let the user log in manually if the profile is not logged in yet.
3. In `js_repl`, attach Playwright with `chromium.connectOverCDP("http://127.0.0.1:<port>")`.
4. Reuse the attached browser and page handles for the rest of the task.

## Defaults

- Default user-data-dir: `D:\Prj\onizuka-playwright-profile`
- Default CDP port: `9222`
- Default login URL: `https://accounts.google.com/`

## Rules

- Do not log into Google from a Playwright-launched Chrome window.
- Do not point Playwright at `%LOCALAPPDATA%\Google\Chrome\User Data`.
- Do use a dedicated user-data-dir that is separate from the user's everyday Chrome profile.
- Do launch Chrome first as a normal browser, then attach Playwright over CDP.
- Do keep the attached CDP browser alive across steps instead of reconnecting unless the process changed.

## Launch

Run:

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

Do not assume launch succeeded just because a command returned.
Only continue when the launch script exits successfully or [scripts/check_cdp_port.ps1](./scripts/check_cdp_port.ps1) confirms the CDP endpoint.

If a stale browser is already using the same profile folder, close it first:

```powershell
powershell -ExecutionPolicy Bypass -File .\scripts\close_logged_in_chrome.ps1
```

## Attach From js_repl

Use a local workspace that already has `playwright` or `playwright-core` installed, then attach:

```javascript
var chromium;
var attachedBrowser;
var attachedContext;
var attachedPage;

{
  const nm = await import("node:module");
  const requireForPw = nm.createRequire("file:///D:/Prj/demo/package.json");
  ({ chromium } = requireForPw("playwright-core"));

  attachedBrowser = await chromium.connectOverCDP("http://127.0.0.1:9222");
  attachedContext = attachedBrowser.contexts()[0];
  attachedPage = attachedContext.pages()[0];
}
```

After attaching, navigate and automate normally.

## Verify Before Automating

- Confirm the browser window is the dedicated profile, not the user's main Chrome.
- Confirm the user has finished manual login if the task depends on Google auth.
- Confirm the CDP endpoint is reachable by running [scripts/check_cdp_port.ps1](./scripts/check_cdp_port.ps1) before attaching if launch behavior looked suspicious.
- If launch times out or the dedicated-profile `chrome.exe` process does not appear, stop and relaunch instead of trying to attach anyway.

## Troubleshooting

Read [references/troubleshooting.md](./references/troubleshooting.md) when:

- Google shows "This browser or app may not be secure"
- `connectOverCDP()` fails
- the CDP endpoint is not reachable
- the launch script returns but no Chrome process is using the dedicated profile
- a stale profile lock prevents launch

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

logged-in-google-chrome

Directory Structure

SKILL.md

Report

Notice