setup-browser-cookies

Import cookies from a real Chromium browser into a headless Playwright browse session.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill setup-browser-cookies-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill setup-browser-cookies-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun.

What problem does it solve? Headless browser sessions start without any logged-in state, so QA testing authenticated pages fails. This Skill imports cookies from your real Chromium browser into the headless browse session so authenticated pages work during testing. ## Core Features & Use Cases - Interactive Cookie Picker: Opens a picker UI in your browser where you select which cookie domains to import, with search and per-domain add/remove controls. - Direct Domain Import: Skip the UI by passing a domain directly, for example importing github.com cookies from a specified browser. - CDP Mode Detection: Detects when browse is already connected to your real browser via CDP and skips the import entirely. - Use Case: Before running QA on an authenticated dashboard, import your session cookies so the headless browser can access logged-in pages without manual login flows. ## Quick Start Ask the assistant to import cookies from your browser so you can test authenticated pages, then pick the domains in the picker UI that opens.

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 gstack browse binary. It detects installed Chromium browsers and opens a picker UI where you select which domains to import into the Playwright session.

How to test authenticated pages with Playwright without logging in?

Import cookies from your real browser into the headless session first. The browse session persists imported cookies between commands, so authenticated pages work immediately in subsequent QA runs.

Can I import cookies from a specific domain only?

Yes, pass the domain directly to skip the picker UI, for example cookie-import-browser comet --domain github.com. Replace the browser name with whichever Chromium browser holds your session.

Does cookie import work when connected via CDP?

No import is needed in CDP mode. When browse is connected to your real browser via CDP, your existing cookies and sessions are already available, and the skill tells you to stop.

Why does cookie import prompt a Keychain dialog on macOS?

Chromium encrypts cookies with a key stored in the macOS Keychain, so the first import per browser triggers an Allow or Always Allow dialog. On Linux, v11 cookies may require secret-tool or libsecret access.