No interface stable Chrome keeps behind a developer switch is exposed
Under the Google Chrome or Chromium brand, claiming Chrome 153 to 156 on desktop: none of GPUResourceTable, GPUSubgroupMatrixConfig, Writer, Rewriter or Proofreader is defined. N/A for other brands, Android and other majors, because features graduate to stable and the list is only valid for the majors it was measured on (severity: warn).
What a detector infers
Stable Chrome keeps unfinished web platform features behind developer switches, and some of them add global interfaces as soon as the switch is on. Measured on 28 October 2026 on Chrome 156 (Linux and Windows): --enable-unsafe-webgpu adds GPUResourceTable and GPUSubgroupMatrixConfig, and --enable-experimental-web-platform-features adds those two and Writer, Rewriter and Proofreader.
None of the five exists in stable Chrome 153, 154, 155 or 156 started without switches, headed or headless, or in Edge 156. Ordinary users almost never run with these switches; server setups often add --enable-unsafe-webgpu so that WebGPU works without a GPU.
How to resolve it
Drop --enable-unsafe-webgpu and --enable-experimental-web-platform-features from the launch arguments. If WebGPU is needed on a machine without a GPU, the software adapter it gets is visible to other rows as well.
Nearby checks in Automation surface
- The user agent names no headless product
headless-ua-tokenBoth of Chrome's headless modes name themselves in the user agent. - A fresh frame has none of Node's, Deno's, Bun's or Pyodide's globals
runtime-globals-absent-in-fresh-frameA new about:blank frame starts with the browser's own globals and nothing else, because no page script has run in it. process, module… - history.replaceState to another origin throws SecurityError
history-replacestate-cross-origin-throwshistory.replaceState may change the URL shown for a document only within its own origin; the HTML standard requires a SecurityError for any… - No automation extension has written its marker into the page
automation-extension-markupSome automation tools announce themselves in the pages they control. - No debugger client attached to this tab after it loaded
console-replay-trapV8 keeps the console messages a page logs, which is why DevTools can show messages logged before it was opened. - 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 /…
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 flag-only-surfaces-absent belongs to.