setup-browser-cookies

Import Chromium browser cookies into a headless session for authenticated testing.

46|13|Updated Jul 30, 2025
One-click install
npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill setup-browser-cookies-aimasteracc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/aimasteracc/tree-sitter-analyzer/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill setup-browser-cookies-aimasteracc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session, enabling authenticated testing without re-login.

Core Features & Use Cases

  • Interactive cookie picker that lets you select which domains to import and applies them to the headless session.
  • Works before QA testing authenticated pages to preserve login state across runs.
  • Browser-agnostic guidance via a setup/check flow and a one-time browser-binary detection.

Quick Start

Use the cookie picker to import domains from your Chromium browser into the 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 cookies from a Chromium browser into a headless session to preserve authentication?

To import cookies from a Chromium browser into a headless session, you can use an interactive cookie picker to select specific domains. This preserves your login state for automated QA testing without requiring a manual re-login.

Do I need a browser binary for automated testing when reusing login state from an existing profile?

Yes, importing login state requires a detected browser binary on your system. The setup flow includes a one-time environment check and browser-binary detection to verify the imported cookies work correctly in the headless session.

Can I select specific domains to import cookies from during headless QA testing?

Yes, an interactive picker allows you to select specific domains to import into the headless session. This targeted approach applies cookies only for the authenticated pages you intend to test, keeping the test environment clean.

What is the best way to maintain authentication state across automated browser tests without re-login?

The best way to maintain authentication across automated browser tests is importing existing session cookies into the headless environment. This skips re-login by applying your real Chromium profile's authenticated state directly to the test run.

Does importing Chromium cookies into headless tests require a separate setup flow before running test suites?

Yes, a one-time setup flow is required before running test suites. This setup includes environment checks, browser-binary detection, and verification of the imported cookies to ensure the headless session maintains the authenticated state.