setup-browser-cookies

Import Chromium browser cookies into headless sessions via an interactive picker UI.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill setup-browser-cookies-tyhuffman7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-setup-browser-cookies
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill setup-browser-cookies-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to preserve login state across QA tests and automated runs.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import before QA testing authenticated pages.
  • Maintains login state across headless sessions to ensure consistent test results.
  • Fast setup for reproducible user contexts during automated checks or manual QA.

Quick Start

Run the setup-browser-cookies skill to import cookies from your real browser and start the picker UI.

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 headless Chromium session?

To import cookies into a headless session, this skill transfers them from your real Chromium browser. It opens an interactive picker UI where you select which cookie domains to load before running authenticated QA tests.

Why do my automated QA tests fail on authenticated pages in headless mode?

Automated QA tests fail in headless mode because the session lacks login state. Importing real browser cookies preserves authentication across headless runs, ensuring consistent and reproducible test results.

Can I select specific cookie domains to import for headless testing?

Yes, you can select specific cookie domains for headless testing. The skill launches an interactive picker UI that lets you choose exactly which authenticated domains to import before executing your automated checks.

Do I need a specific environment to import cookies for automated browser sessions?

Yes, you need a gstack-enabled environment to import cookies for automated browser sessions. This prerequisite ensures the headless Chromium instance can properly access and preserve your real browser login state.

What is the best way to maintain login state across headless browser sessions?

The best way to maintain login state across headless sessions is importing cookies from a real Chromium browser. This approach provides fast setup for reproducible user contexts during manual or automated QA testing.