setup-browser-cookies

You can import authenticated browser cookies into a Playwright session by using a skill that extracts and injects session data from local Chromium browser profiles. This enables headless authentication for automated workflows.

Yes, you can use an existing local browser session for automated QA testing by importing your active session cookies. This eliminates the friction of manually logging into web applications during headless test execution.

To select specific domains when importing browser cookies for headless automation, you invoke the skill to open an interactive cookie picker. You then choose the exact domains you need to authenticate from your local browser profiles.

Yes, you need the gstack browse binary to decrypt and inject session data. It is required to access local Chromium browser profiles and extract the authenticated session cookies into the headless environment.

Automated agents fail to access protected pages requiring login because headless sessions start unauthenticated. You must import existing authenticated session cookies from a local Chromium browser to grant the agent immediate access.

Importing session cookies for headless automation only works with local Chromium-based browsers. The skill specifically requires access to Chromium browser profiles to decrypt and inject the session data into Playwright.