setup-browser-cookies

Imports cookies from browsers into headless Playwright sessions for authenticated testing.

Updated Mar 19, 2026

Search Tags:#automation #qa #playwright #sessions #browser #import #cookie

Ready to run

npx skills add https://github.com/shaneholloman/ship --skill setup-browser-cookies-shaneholloman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/shaneholloman/ship/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/shaneholloman/ship --skill setup-browser-cookies-shaneholloman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often need to test authenticated flows but don't want to rely on manual login or flaky mocks. This skill imports cookies from real browsers into the headless browse session so tests run with valid session data.

Core Features & Use Cases

Interactive domain picker: choose which sites to import from Chrome, Arc, Brave, Edge, and Comet.
Safe, decrypted cookies: loads cookies into Playwright sessions without exposing values in the UI.
Quick setup: one-time binary setup to enable cookie import in CI or local QA runs.

Quick Start

Run the cookie import workflow to load cookies from your browser into the headless Playwright 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 real browser cookies into a Playwright session for authenticated testing?▼

To import cookies into Playwright sessions, you use an interactive picker to select target domains from local browsers like Chrome, Arc, Brave, Edge, and Comet, which decrypts and loads the session data automatically.

Can I load cookies from Chrome or Arc into headless QA sessions without manual login?▼

Yes, you can load cookies from Chrome, Arc, Brave, Edge, and Comet into headless QA sessions. The tool locates and decrypts the browser cookie store to inject valid session data directly.

What is the best way to handle authenticated flows in Playwright without using flaky mocks?▼

The best way to handle authenticated flows is importing real, decrypted cookies from your active browser into the headless Playwright session. This bypasses manual logins and avoids flaky mocks by using valid session data.

Do I need a specific setup to decrypt browser cookies for QA automation?▼

Yes, you need a one-time setup of the cookie-import-binary and ship tooling. This configures the environment to locate and decrypt the browser cookie store for your current automation sessions.

Are imported cookie values exposed in the user interface during the automation process?▼

No, imported cookie values are not exposed in the user interface. The tool safely loads decrypted cookies into the Playwright session in the background to maintain security while testing authenticated flows.

Why do my Playwright tests fail when trying to bypass authentication with sessions?▼

Playwright tests fail when sessions are invalid or mocked. Importing real, decrypted cookies from a live browser session into the headless environment ensures the automation runs with valid authentication data.