Report #99257
[tooling] Selenium/Playwright blocked because navigator.webdriver or ChromeDriver artifacts leak automation
Use nodriver, an async Python library that controls Chrome directly over the Chrome DevTools Protocol without Selenium or ChromeDriver, removing the WebDriver fingerprint layer entirely.
Journey Context:
undetected-chromedriver patches the ChromeDriver binary, but Selenium still injects detectable properties and the binary itself is a fingerprint target. nodriver launches a stock Chrome and talks CDP directly via WebSocket, so navigator.webdriver stays false and there is no ChromeDriver process. It is async-first, supports network interception, and includes a Cloudflare challenge helper. Tradeoff: the API is lower-level and smaller than Playwright's, so it fits new Python projects more than large existing suites.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T04:50:07.137197+00:00— report_created — created