setup-browser-cookies

Imports cookies from Chromium browsers into a headless Playwright session for authenticated testing.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill setup-browser-cookies-computerconnection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill setup-browser-cookies-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session so tests can run with authenticated pages without manual login.

Core Features & Use Cases

  • Interactive cookie picker UI to select which cookie domains to import.
  • Decrypts and loads cookies into the Playwright session used for headless testing.
  • Supports major Chromium browsers (Comet, Chrome, Arc, Brave, Edge) for QA authentication workflows.
  • Use before QA testing authenticated pages to streamline setup.

Quick Start

Open the cookie picker, select the domains to import, then confirm when you're finished.

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 cookies from a real browser into a headless Playwright session?

To import cookies into a headless Playwright session, use an interactive cookie picker UI to select target domains. The tool decrypts and securely loads real browser cookies, enabling authenticated QA testing without manual login.

Can I use cookies from Chrome or Edge for authenticated QA testing?

Yes, you can use cookies from Chrome or Edge for authenticated QA testing. The tool supports major Chromium browsers including Chrome, Arc, Brave, Comet, and Edge, decrypting their cookies for use in headless sessions.

What is the best way to run automated tests on authenticated pages without manual login?

The best way to run automated tests on authenticated pages without manual login is importing real browser cookies into a headless session. This bypasses login forms entirely by securely loading decrypted cookies from your active browser profile.

Does this cookie import tool support multiple domains for cross-domain QA flows?

Yes, the cookie import tool supports multiple domains for cross-domain QA flows. You can select multiple cookie domains through the interactive picker UI before confirming the import into your headless Playwright testing session.

Why do my headless browser tests fail to authenticate on pages requiring login?

Headless browser tests fail authentication because they start with empty cookie stores. Importing decrypted cookies from a real browser profile into the headless Playwright session solves this by restoring the required authenticated state.

Do I need a specific Chromium browser to extract cookies for headless automation?

You need a supported Chromium browser to extract cookies for headless automation. Compatible browsers include Comet, Chrome, Arc, Brave, and Edge, ensuring your real browser cookies can be decrypted and loaded into the testing session.