OneGlanse

Engineering case study

Why OneGlanse Uses Camoufox Instead of Chromium

OneGlanse collects answers from the browser interfaces of ChatGPT, Perplexity, Gemini, Claude, and Google AI Overview. The browser is part of the collection infrastructure, not just a way to render a page.

OneGlanse originally used Chromium. Keeping it reliable on VPS infrastructure gradually turned browser fingerprinting into its own project. In March 2026, OneGlanse moved to Camoufox, a modified Firefox browser built for automated browsing.

The original Chromium approach

The project tried direct Chrome DevTools Protocol (CDP) control, Playwright Chromium, a short Selenium experiment, Rebrowser Playwright, real Google Chrome in the VPS image, and a Chrome extension with native messaging. Its custom fingerprint code modified or generated many browser properties:

  • Screen, viewport, and window dimensions
  • Browser version, user agent, and client hints
  • Operating system and hardware properties
  • Fonts, WebGL, and canvas output
  • Languages, locale, timezone, and geolocation
  • Worker-context browser properties

VPS execution added virtual displays, sparse system fonts, profiles, proxy identity, and session state. The project also experimented with profile warmups, mouse movement, scrolling, and variable typing. Each change had a reason. Keeping all of the signals consistent was the harder task. A browser that reports one operating system while exposing another system's fonts or graphics properties can stand out more, not less.

The browser was becoming its own project

The repository records the progression. Each item below links to the commit that introduced or expanded the work.

  1. March 4, 2026: Moved from direct CDP control to Playwright Chromium
  2. March 4, 2026: Tried Selenium with Playwright/CDP before returning to Playwright
  3. March 7, 2026: Tried Rebrowser Playwright
  4. March 7, 2026: Expanded custom fingerprint handling
  5. March 7, 2026: Adjusted the VPS browser fonts
  6. March 8, 2026: Installed Google Chrome and added sticky proxy sessions and profiles
  7. March 9, 2026: Tried a Chrome extension and native messaging
  8. March 27, 2026: Replaced the custom Chrome browser layer with Camoufox
  9. March 29, 2026: Removed hardcoded OS, screen, and fingerprint overrides

The problem was not that Chromium cannot be automated. OneGlanse was taking responsibility for an increasingly large browser identity layer while its main job was collecting and analyzing AI product responses.

Why Camoufox changed the boundary

Camoufox modifies Firefox itself. It handles many fingerprint properties inside the browser, instead of relying mainly on JavaScript patches after a page loads. Its launcher uses BrowserForge to generate plausible combinations of device, screen, locale, font, and graphics properties. Playwright controls it through Firefox's Juggler path rather than Chromium's CDP path.

That let OneGlanse focus on the parts specific to AI visibility collection: authenticated sessions, proxy management, provider navigation, prompt submission, response stabilization, citations, and retries. The March 29 refactor removed several hardcoded fingerprint overrides and delegated more of that work to Camoufox.

Camoufox does not eliminate bot detection

Provider interfaces can still challenge automated traffic. Datacenter IP reputation, blocked proxies, expired sessions, UI changes, CAPTCHAs, Cloudflare, Turnstile, and rate limits still matter. OneGlanse still detects challenge pages and handles proxy failures. Camoufox is one part of collection, not a promise that browser sessions will never be detected.

Moving to Camoufox reduced the custom fingerprint code OneGlanse needed to maintain. That is an engineering observation from this project, not a controlled benchmark of detection rates.

Why the browser matters here

A product interface can include retrieval, citations, source cards, and ordering that differ from a model API response. OneGlanse uses the browser to observe that product surface. The browser choice therefore affects the reliability of the data it can collect, even though the analysis step runs separately.

Credit to Camoufox

OneGlanse's collection layer depends on the work of the Camoufox contributors. The project began at daijro/camoufox. Current browser development also occurs at Clover Labs. OneGlanse currently installs the `cloverlabs-camoufox` Python package. These contributors maintain the browser layer that lets OneGlanse spend more effort on collection and analysis.

For the wider infrastructure tradeoff, read why OneGlanse is self-hosted. For how a collected answer is interpreted, read the collection methodology.