setup-browser-cookies

Import cookies from real browsers into a headless Playwright session.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/yolopunk/jedi --skill setup-browser-cookies-yolopunk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/yolopunk/jedi --skill setup-browser-cookies-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps QA and developers quickly import cookies from real browsers into a headless Playwright session, ensuring authenticated test flows without repeated logins.

Core Features & Use Cases

  • Import cookies from popular browsers (Comet, Chrome, Arc, Brave, Edge) into your automated tests.
  • Use an interactive picker UI or direct domain import to select which cookie domains to load.
  • Handle common prompts (system keychain) and verify the cookie load before starting tests.

Quick Start

Run the setup-browser-cookies skill to initialize the picker, select domains, and import cookies into your headless session.

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 Playwright session?

To import browser cookies into a headless Playwright session, run the setup-browser-cookies skill to initialize the picker, select your target domains, and load the authenticated cookies directly into your automated test flow.

Can I use cookies from Chrome and Arc for Playwright test automation?

Yes, you can use cookies from Chrome, Arc, Brave, Edge, and Comet for Playwright test automation by detecting the local browser profiles and importing their authenticated session cookies into your headless tests.

What is the best way to preserve authentication in automated tests without repeated logins?

The best way to preserve authentication in automated tests without repeated logins is importing cookies from a real browser profile into your headless session, bypassing multi-step authentication flows during QA pipeline execution.

How do I select specific domains when importing cookies for QA automation?

You can select specific domains when importing cookies for QA automation by using the interactive domain picker UI or by configuring a direct domain import to target only the authenticated sessions your tests require.

Do I need to configure system keychain permissions to extract browser cookies?

Yes, you need to handle system keychain prompts during the one-time setup to allow the local browser-detection binary to read and extract cookies from your real browser profiles into the headless session.