Verified 2026-10-20:browser.cloud_provider: steel, browser.engine: camofox,
browser.headed: true, browser.inactivity_timeout: 450, browser.use_gateway: false,
browser.camera_provider: camofox, browser.allow_private_urls: true,
browser.allow_unsafe_evaluate: true, browser.cdp_url: '',
browser.command_timeout: 185.
browser.camofox: → adopt_existing_tab: true, managed_persistence: true,
rewrite_loopback_urls: true, user_id: anthony.
Note inactivity_timeout is 450s, not the 120s recorded here — that value changed.
cloud_provider is steel with engine: camofox; the two keys describe different layers.
Live processes (2026-10-20):cua-driver serve (PID 3312393), camoufox-ws-server.mjs,
and a live camoufox-bin (FirefoxDev build) tree under /home/hermes/.cache/camoufox/.
Camofox's REST port 9377 is not listening on CT460 — the Camofox browser service runs on
CT450; see systems/browser-backend.
Runs headed under Xvfb rather than a true headless mode, per systems/headless-server — fluxbox provides the window manager, x11vnc/noVNC expose it for human viewing.
cua-driver bridges Hermes's computer-use tool calls to the browser.
Chrome (not found in use)
No google-chrome, chromium, or CDP-only launch flags found in the sanitized config or running process list during this audit.
Included in the comparison because the page existed as a placeholder — if Chrome/CDP was evaluated and rejected, that reasoning isn't captured anywhere; worth a decisions/index entry if anyone remembers why Camoufox was chosen over stock Chrome.
Verdict
This install uses Camoufox exclusively (via the cua-driver + camoufox-ws-server.mjs stack
on CT460 and a separate Camofox service on CT450). There's no evidence Chrome/Chromium was ever wired in as an alternative on this host — the comparison exists more as a placeholder for a decision that may have been made outside this wiki than as an active either/or choice today.