Files
agent-estate-wiki/comparisons/camoufox-vs-chrome.md
T
Tony0410andHermes 677bb0c959 docs(wiki): correct Steel Browser references across 15 pages — Steel fully removed, Camofox is sole backend
Root cause of the long-standing cloud_provider: steel residue: the 2026-07-30
rollback disabled the browser-steel plugin and set browser.engine: camofox but
left browser.cloud_provider: steel in config.yaml. The split config was
inert-but-wrong, so it survived ~3 months of audits unnoticed.

Corrects pages that still described Steel as present, running or configured:
- systems/browser-backend.md (incl. gateway-restart env-var note)
- comparisons/steel-vs-camoufox.md, comparisons/camoufox-vs-chrome.md
- decisions/rollback-steel-to-camofox.md, decisions/index.md
- infrastructure/docker-services.md, infrastructure/tailscale.md, infrastructure/hosts.md
- systems/homepage-dashboard.md, systems/scheduled-tasks.md
- concepts/browser-automation.md, runbooks/recover-docker-service.md
- current-state.md, index.md, agents/nanobot.md
- log.md (dated entry; supersedes the 00:3x audit's 'endpoint dark' wording)

Also restores the Ignis compose row in infrastructure/docker-services.md, which
the 2026-10-11 revision dropped (verified: /home/hermes/docker/ignis/docker-compose.yml
exists and the ignis container is Up on CT460).

Co-Authored-By: Hermes <hermes@local>
2026-10-29 02:02:49 +08:00

3.3 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Camoufox vs Chrome comparison active 2026-07-22 2026-10-29 2026-10-29 medium
comparison
browser
raw/configs/hermes-config-sanitized.txt

Camoufox vs Chrome

Purpose

Compare the two browser-automation options for Hermes's browser tool.

At a glance

Camoufox Chrome
In use on this install Yes — configured cloud_provider No evidence found
Config browser.camofox.managed_persistence: true (note: key is spelled camofox in config, not camoufox) n/a
Driver cua-driver v0.28.2 at /home/hermes/.local/bin/cua-driver (the 0.9.0 release path this page used to cite no longer exists) n/a
Display Headed, via Xvfb :99 + fluxbox — see systems/headless-server n/a
use_gateway false n/a

Detail

Camoufox (in use)

  • 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. Superseded 2026-10-29: cloud_provider now reads camofox (with camera_provider: camofox, engine: auto, cdp_url: ""), and Steel is fully removed from the estate — the browser-steel plugin is deleted and there is no Steel fallback path. → systems/browser-backend
  • 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.