setup-browser-cookies

To import cookies into a headless browser session, you need a running Playwright or Puppeteer session and a local Chromium browser profile. Use the interactive cookie picker UI to select domains and load real authentication cookies for automated tests.

Yes, you can simulate authenticated user access by importing per-domain cookies from your real Chromium browser profile into the headless session. This bypasses manual logins during QA testing workflows.

Cookie import works specifically across Chromium-based browsers. It requires a local Chromium browser profile to extract the authentication cookies and a running Playwright or Puppeteer session to load them.

You select specific domains using the interactive cookie picker UI. Simply ask to import cookies to launch the picker, then choose the desired domains to load their corresponding authentication states into the headless browsing session.

The best way to handle login states in headless automation is importing cookies from a local Chromium profile. This one-time setup and per-session cookie loading approach eliminates the need for scripted manual logins in your test suite.

Yes, a running Playwright or Puppeteer session is required. The cookie picker UI loads extracted cookies directly into the active headless browsing context to establish the authenticated session for testing.