Skip to main content
Home/Recipes/Extract authenticated views via CDP
Extraction

10.Extract authenticated views via CDP

Developer

Overview

Connect Dembrandt to an existing Chrome session via CDP to extract pages that require login — dashboards, account settings, gated product UIs — without automating the auth flow.

Dembrandt normally opens a fresh headless browser with no session. Pages behind a login wall return the unauthenticated view. The BROWSER_CDP_ENDPOINT environment variable lets Dembrandt connect to an existing Chromium instance via the Chrome DevTools Protocol instead. Log in manually in that browser, then point Dembrandt at it. The extraction runs in your authenticated session, capturing the real dashboard or gated UI that anonymous extraction cannot reach.

Launch Chrome with remote debugging

Terminal
google-chrome --remote-debugging-port=9222

Extract authenticated view

Terminal
BROWSER_CDP_ENDPOINT=http://localhost:9222 dembrandt app.company.com/dashboard --save-output
macOS: launch Chrome with CDP
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 --user-data-dir=/tmp/chrome-cdp
# Log into the target site in this Chrome window, then run:
BROWSER_CDP_ENDPOINT=http://localhost:9222 dembrandt app.company.com/dashboard --save-output
Output

Token extraction from authenticated product UIs, dashboards, and gated views.

More in Extraction

1.Basic token extraction2.Multi-page crawl3.Dark mode analysis4.Mobile vs. desktop token comparison5.Screenshot + token visual audit6.DTCG export to Tokens Studio or Figma Variables7.Extract specific paths and merge8.Raw vs. filtered color analysis9.Extract Cloudflare-protected sites with Firefox

Browse all

All recipes →

43 workflows