skills.rest
sadie100
sadie100COMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Migrate authenticated cookie states from real to headless Chromium sessions.

Updated Apr 8, 2026
Search Tags:#browser automation#QA testing#headless browser#browser cookies#session simulation
One-click install
npx skills add https://github.com/sadie100/claude-dotfiles --skill setup-browser-cookies-sadie100
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/sadie100/claude-dotfiles/tree/main/skills/setup-browser-cookies
Command: npx skills add https://github.com/sadie100/claude-dotfiles --skill setup-browser-cookies-sadie100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gstack, chromium, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manages the challenge of ensuring headless browser sessions have the necessary cookies to authenticate and simulate a user's logged-in browser state across different machines.

Core Features & Use Cases

  • Import Browser Cookies: Migrate logged-in session cookies from a real Chromium browser to a headless browser session for testing.
  • Session Simulation: Enable the headless browser to mimic user actions by accessing session-based resources.
  • Use Case: Ideal for automated QA testing on websites requiring authentication, allowing the automated browser to simulate login sessions for end-to-end testing.

Quick Start

Use the command 'setup-browser-cookies' to import cookies from your main Chromium browser session into the headless browser session for your testing environment.

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 for QA testing?▼

To import browser cookies into a headless browser session, use the 'setup-browser-cookies' command to migrate authenticated session states from a real Chromium browser directly into your headless testing environment.

Can I simulate a logged-in user state in a headless Chromium browser?▼

Yes, you can simulate a logged-in user state in a headless Chromium browser by migrating authenticated cookie states from your real browser session, allowing automated tests to access session-based resources without manual login steps.

What's the best way to handle session-based authentication in automated browser testing?▼

Handling session-based authentication in automated browser testing is best done by migrating real browser cookies into headless sessions, ensuring consistency across test environments using gstack without repeating manual login processes.

Do I need gstack and Chromium to use this browser cookie migration approach?▼

Yes, you need both gstack and Chromium, as gstack ensures consistency across test environments and the cookie migration specifically targets transferring authenticated states from a real Chromium browser to a headless one.

Why does my headless browser session lose authentication state across different machines?▼

Headless browser sessions lose authentication state across different machines because they lack the necessary session cookies by default; migrating authenticated cookie states from a real browser resolves this for QA automation.

Related Skills

Explore More Software Engineering Skills→
nhattran998nhattran998

setup-browser-cookies

Import cookies from a Chromium browser into a headless session.

Community
Intermediate
ManzuetiManzueti

setup-browser-cookies

Import cookies from a Chromium browser into a headless browser session.

Community
Basic
billydeeii136billydeeii136

setup-browser-cookies

Import cookies from a Chromium browser into a headless browser session.

Community
Intermediate
ComputerConnectionComputerConnection

setup-browser-cookies

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

Community
Intermediate