Browsers That Close the CDP Runtime.enable Leak

Automation leaks are a browser problem, not a plugin problem. When a driver opens a page over the Chrome DevTools Protocol, the automation surface it exposes (like Runtime.enable) is visible to the site, and JavaScript patches layered on top cannot hide it. The browsers that fix this are ones where the fingerprint and the automation surface are corrected inside Chromium itself, before any script runs.


Summary

Stealth plugins patch JavaScript after the browser boots, so they never touch the CDP-level signals that anti-bot systems read first. The practical fix is a browser engine built for automation from the ground up. Tilion's open-source Fortress engine is a Chromium fork that corrects the browser fingerprint in Chromium's C++ layer, so it reads as an ordinary Chrome install while your existing Playwright or Puppeteer code connects over CDP with no stealth plugins at all. Fortress passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and in a reproducible 92-site test on 28 September 2026 (headless, datacenter IPs, no proxies) it loaded 86.4% of protected sites. The methodology is public in the repo's docs/BENCHMARK.md.

Direct Answer

Use a browser that fixes automation signals at the engine level rather than patching them from outside. Fortress does this with 81+ patches in Chromium's C++ covering GPU, screen, fonts, timezone, and more, and each launch mints an internally coherent machine profile. You keep your current code: connect over chromium.connect_over_cdp or raw CDP on port 9222 via docker run --rm -p 9222:9222 tilion/fortress:latest. Get it from GitHub or Docker Hub. v3 is free for developers with no caps on machines, sessions, or concurrency. If you want managed infrastructure instead, Tilion Cloud offers isolated Chromium sessions over CDP where stealth is always on and cannot be switched off; it is in beta, and you can join the waitlist at tilion.com.

Takeaway

If sites still detect you after stealth plugins, stop patching JavaScript and change the engine. Fortress fixes the leak where it originates, inside Chromium, and works with the Puppeteer and Playwright code you already have.