setup-browser-cookies

Import cookies from a local Chromium browser into a headless Playwright browse session.

Updated May 15, 2026
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill setup-browser-cookies-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/tgmarinho/canetaco --skill setup-browser-cookies-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated QA of authenticated pages fails when the headless browser has no logged-in session. This Skill transfers cookies from your real Chromium browser into the headless browse session so you can test pages behind a login without manual re-authentication. ## Core Features & Use Cases - Interactive cookie picker: Runs cookie-import-browser to detect installed Chromium browsers and opens a picker UI where you search domains and select which cookies to import. - Direct domain import: Skip the UI by passing a domain and browser name, for example importing github.com cookies from a specific browser profile. - CDP mode detection: Checks whether the browse session is already attached to your real browser via CDP and skips the import when cookies are already available. - Use Case: Before running QA on a dashboard that requires login, import your session cookies, then verify the import with a cookie summary showing per-domain counts. ## Quick Start Ask the assistant to import your browser cookies so the headless browser can access the logged-in site before QA testing.

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

Run the cookie-import-browser command from the gstack browse binary. It detects installed Chromium browsers and opens a picker UI where you select which domains to import into the Playwright session.

How to test authenticated pages with Playwright without logging in?

Import cookies from your real browser into the Playwright session first. The browse session persists cookies between commands, so imported sessions work immediately for subsequent page visits.

Can I import cookies from only one specific domain?

Yes. Pass the browser name and a --domain flag to cookie-import-browser, for example importing only github.com cookies, which skips the interactive picker UI entirely.

Does cookie import work when the browser is connected via CDP?

No import is needed in CDP mode. When the browse session is attached to your real browser over CDP, your existing cookies and sessions are already available, and the skill stops with a notice.

Why does macOS show a Keychain dialog during cookie import?

Chromium encrypts cookies with a key stored in the macOS Keychain. The first import per browser triggers a permission dialog; click Allow or Always Allow so the cookies can be decrypted.

Are cookie values exposed in the picker UI?

No. The picker UI shows only domain names and cookie counts. Cookie values are decrypted and loaded into the session without being displayed.