setup-browser-cookies

Import cookies from installed Chromium browsers into a headless Playwright browse session.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill setup-browser-cookies-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/setup-browser-cookies
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill setup-browser-cookies-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Headless browser sessions start without any login state, so QA testing authenticated pages requires manually recreating sessions. This Skill imports cookies directly from your real browsers so the headless session is already logged in. ## Core Features & Use Cases - Interactive Cookie Picker: Detects installed Chromium browsers (Comet, Chrome, Arc, Brave, Edge) and opens a picker UI where you select which cookie domains to import. - Direct Domain Import: Skip the UI by specifying a browser and domain, such as importing github.com cookies from Comet in one command. - Session Verification: Lists imported cookies grouped by domain so you can confirm the headless session is authenticated before testing. - Use Case: Before running QA tests against a staging site that requires login, import your existing browser cookies so the headless Playwright session can access authenticated pages immediately. ## Quick Start Ask the assistant to import cookies from your browser so the headless session is logged in before testing authenticated pages.

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?

Run the cookie-import-browser command, which detects installed Chromium browsers and opens an interactive picker UI. Select the domains you want to import, and the cookies are decrypted and loaded into the Playwright session.

Which browsers are supported for cookie import?

The tool auto-detects installed Chromium-based browsers including Comet, Chrome, Arc, Brave, and Edge. You can switch between detected browsers inside the picker UI or specify one directly on the command line.

Can I import cookies for a specific domain without the UI?

Yes, pass the browser name and domain directly, for example cookie-import-browser comet --domain github.com. This skips the picker UI and imports only that domain's cookies.

Why does macOS show a Keychain dialog when importing cookies?

The first import per browser triggers a macOS Keychain prompt because Chromium cookies are encrypted with a key stored in the Keychain. Click Allow or Always Allow so the tool can decrypt the cookies.

Are cookie values exposed in the picker UI?

No, the picker UI only shows domain names and cookie counts. Cookie values are never displayed, and imported cookies persist in the browse session between commands.