setup-browser-cookies

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

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/psyche911/AntigravityTest --skill setup-browser-cookies-psyche911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/psyche911/AntigravityTest/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/psyche911/AntigravityTest --skill setup-browser-cookies-psyche911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Headless browser sessions start without any logged-in state, so QA testing authenticated pages fails or requires manual re-login. This Skill transfers cookies from your real browser into the headless session so authenticated pages work immediately. ## Core Features & Use Cases - Interactive Cookie Picker: Detects installed Chromium browsers (Comet, Chrome, Arc, Brave, Edge) and opens a picker UI where you select which 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 Persistence: Imported cookies persist in the browse session between commands and can be verified with a summary of domain counts. - Use Case: Before running automated QA on a staging site that requires login, import your authenticated session cookies so the headless browser can access protected pages. ## 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, then select the domains to import. Alternatively, pass a browser name and domain directly to skip the UI.

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.

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

Yes, run cookie-import-browser with the browser name and a --domain flag, for example comet --domain github.com. This imports that domain's cookies directly without opening the picker.

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

The first import per browser may trigger a macOS Keychain prompt because browser cookies are encrypted with a key stored in the Keychain. Click Allow or Always Allow to let the tool decrypt the cookies.

Are my cookie values exposed in the picker UI?▼

No, the picker UI only displays domain names and cookie counts. Cookie values are decrypted and loaded into the Playwright session without being shown in the interface.