DevTools Runtime serialization is not active
No stack read without an attached Runtime client. On a post-May-2025 V8 there is no stack read either way, which is why the sibling row exists.
What a detector infers
An attached DevTools Runtime domain serialises console arguments and reads an Error stack accessor. Human DevTools does the same, so this is contextual and unscored.
Read this row together with console-preview-proxy-trap, which asks the same question through a different subsystem: two V8 commits in May 2025 added a getErrorProperty() wrapper that extracts the accessor and skips it when its ScriptId shows a script wrote it, so on a current Chrome this probe answers "no" whether or not a Runtime client is attached.
A quiet row here is therefore not evidence of a clean environment on its own — it is a vector that was closed, and the honest way to state that is to keep the row and say so rather than let a patched signal read as a pass.
How to resolve it
Detach Runtime.enable when unnecessary.
Read in the wild by
Rebrowser
Uses the Error.stack console-serialization side effect.
index.js runtimeEnableTest
Rebrowser bot detectorEvery attribution traces to a published artifact. See the sources and their limits.
Nearby checks in Automation surface
- navigator.webdriver does not assert WebDriver control
webdriver-offThis check is intentionally one-way. The WebDriver specification defines navigator.webdriver as the browser's assertion that it is under… - navigator.webdriver is a native prototype getter returning false
webdriver-descriptor-integrityRather than reading the value, this check inspects the property's shape: it requires a getter on Navigator.prototype whose… - no Selenium / Puppeteer / Playwright globals
automation-globalsThis check tests a fixed list of roughly two dozen known names against both window and document (Selenium's __webdriver_evaluate /… - no anti-detect fingerprint setters left on window
antidetect-fingerprint-settersAnti-detect browsers in the Camoufox family apply a per-context fingerprint through helper functions published on the window object… - No console preview enumerated a prototype-chain Proxy
console-preview-proxy-trapDevTools has to look inside an object to show it to you, and in JavaScript looking inside an object is an observable act. - No Puppeteer / Playwright sourceURL marker
sourceurl-leakPuppeteer and Playwright evaluation labels can appear in main-world Error stacks. - No controller code crossed the main-world canary
main-world-executionAn early DOM canary records main-world calls, but page code and extensions can also call it, so this is contextual. - No exposed Puppeteer / Playwright binding
exposed-binding-leaksExposed functions leave Playwright/Puppeteer registries, prefixes, source text, or __installed markers.
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Automation surface checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Automation surface — the family runtime-enable-leak belongs to.