Report #100203
[tooling] Selenium/Playwright still detected because of WebDriver artifacts, navigator.webdriver, or CDP leaks
Switch to nodriver \(or the community fork zendriver\): pure Python async control of Chrome over the Chrome DevTools Protocol with no Selenium/ChromeDriver binary. Launch with await uc.start\(\), navigate pages, evaluate JS, and intercept requests via CDP events.
Journey Context:
Patching Selenium with stealth flags is an arms race; the WebDriver process and injected variables \(cdc\_, navigator.webdriver\) are detectable. nodriver removes the middleman entirely and connects Python directly to Chrome over CDP, avoiding driver-injected markers. It is async-only and lighter than Playwright. Tradeoff: smaller ecosystem, no built-in humanized mouse paths, and proxy auth can be awkward. zendriver is the more actively maintained community fork.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T04:50:00.669074+00:00— report_created — created