Files
agent-estate-wiki/comparisons/camoufox-vs-chrome.md
T

70 lines
4.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: Camoufox vs Chrome
type: comparison
status: active
created: 2026-07-22
updated: 2026-11-20
verified_on: 2026-11-20
confidence: medium
tags: [comparison, browser]
sources: [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.
> **Re-verified 2026-11-20 (stocktake).** Live config unchanged: `cloud_provider: camofox`,
> `camera_provider: camofox`, `engine: auto`, `headed: true`, `inactivity_timeout: 450`,
> `use_gateway: false`, `cdp_url: ""`, `camofox.managed_persistence: true`, `user_id: anthony`.
> `cua-driver` still **v0.28.2**; `cua-driver serve` + `camoufox-ws-server.mjs` + a `camoufox-bin`
> tree all running on CT460 (under Xvfb `:99` 1600×1200 + fluxbox).
> **Correction:** ~~Camofox's REST port 9377 is not listening on CT460 — the service runs on CT450~~ —
> `:9377` **is listening on CT460** (`node`, `/health` → `ok`, engine `camoufox`); the service is the
> local `systemd --user` unit `camofox-browser.service` (active), per [[systems/browser-backend]]'s
> 2026-10-13 correction. The CT450 attribution is dead. The ws-server also listens on `:9222` (CDP).
> No Chrome/Chromium process found in this probe either.
### 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.
## Related
- [[systems/browser-backend]]
- [[concepts/browser-automation]]