setup-browser-cookies

Import cookies from installed Chromium browsers into a headless Playwright browse session.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill setup-browser-cookies-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill setup-browser-cookies-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing authenticated pages with a headless browser normally requires re-entering credentials or manually scripting login flows. This Skill transfers existing logged-in sessions from your real browser into the headless browse session so QA testing can start immediately. ## Core Features & Use Cases - Interactive Cookie Picker: Detects installed Chromium browsers (Comet, Chrome, Arc, Brave, Edge) and opens a picker UI to select which cookie domains to import. - Direct Domain Import: Skip the UI by specifying a browser and domain directly, such as importing github.com cookies from Comet. - Session Verification: Lists imported cookies grouped by domain to confirm the headless session is authenticated. - Use Case: Before running automated QA on an authenticated dashboard, import your existing login cookies so the headless browser accesses protected pages without a scripted login flow. ## Quick Start Ask the assistant to import your browser cookies for a domain like github.com so the headless browse session can access authenticated pages.

Frequently Asked Questions about setup-browser-cookies

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

FAQPage Schema
How do I import browser cookies into a headless browser session?▼

Run the cookie-import-browser command from the browse binary to open an interactive picker UI in your default browser. Select the domains you want to import, and the cookies are decrypted and loaded into the Playwright session.

How to test authenticated pages with Playwright without logging in?▼

Import your existing logged-in session cookies from your real browser into the headless session first. The browse session persists cookies between commands, so authenticated pages work immediately after import.

Which browsers are supported for cookie import?▼

The tool auto-detects installed Chromium-based browsers including Comet, Chrome, Arc, Brave, and Edge. You can switch between detected browsers inside the picker UI or specify one directly on the command line.

Can I import cookies for a specific domain without the UI?▼

Yes, pass the browser name and domain directly, for example cookie-import-browser comet --domain github.com. This skips the picker UI and imports only that domain's cookies.

Why does macOS show a Keychain dialog during cookie import?▼

Chromium cookies are encrypted with a key stored in the macOS Keychain, so the first import per browser triggers an access prompt. Click Allow or Always Allow to let the tool decrypt the cookies.

Are cookie values exposed in the picker UI?▼

No, the picker UI only displays domain names and cookie counts. Cookie values are never shown, and the picker is served on the same port as the browse server with no extra process.