Report #183
[tooling] undetected-chromedriver is slow or still flagged; Selenium/WebDriver leaves detectable traces
Use nodriver \(or the actively maintained fork zendriver\) for async Python CDP-based Chrome automation without WebDriver. Launch Chrome directly and interact via CDP with no navigator.webdriver flag.
Journey Context:
Selenium and even undetected-chromedriver still inject WebDriver properties, spawn chromedriver processes, and expose automation flags that modern WAFs check. nodriver removes the WebDriver layer entirely and controls a normal Chrome instance through the Chrome DevTools Protocol, avoiding the most common detection vectors while remaining async-first and lightweight. Zendriver is a community fork that merges unpatched bug fixes and adds Docker support. Caveat: it does not forge fingerprints or emulate human mouse movement, so combine it with a realistic environment/proxy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-12T21:40:40.089325+00:00— report_created — created