Files
agent-estate-wiki/comparisons/steel-vs-camoufox.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

84 lines
5.5 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: Steel Browser vs Camoufox
type: comparison
status: active
created: 2026-07-29
updated: 2026-10-29
verified_on: 2026-10-29
confidence: high
tags: [comparison, browser, steel, camofox, decision]
sources: [live-probe, session-history]
---
# Steel Browser vs Camoufox
## Purpose
Compare the two browser-automation backends Hermes has used, including the Jul 29–30 experiment and the decision to revert. **Camofox is now the only backend available — Steel was fully removed on 2026-10-29.**
## At a glance
| | Steel Browser (CT201) | Camofox (systemd --user on CT460) |
|---|---|---|
| **In use** | **Removed 2026-10-29** (primary 2026-07-29 → 07-30) | **Yes** — the only backend |
| **Engine** | Chromium 140 (Playwright) | Camoufox (Firefox-based) |
| **Connection** | CDP (`ws://` via port 9223) | REST API + CDP WebSocket, both `localhost:9377` |
| **API** | REST at `:3000` — create/destroy/query sessions | Camoufox REST + CDP WebSocket |
| **Headless** | Native headless | Xvfb + VNC (headed, anti-fingerprint) |
| **Container** | Docker on CT201 — **removed 2026-10-29** | `systemd --user` unit on the Hermes host (CT460) |
| **Stealth** | Standard Chromium | Anti-detection fingerprinting |
| **Session viewer** | Built-in UI at `/steel` — **route deleted** | VNC at `/vnc-camofox` |
| **Plugin** | `browser-steel` — **deleted 2026-10-29** | Native Hermes `browser.cloud_provider: camofox` |
## The Steel Experiment (Jul 29–30)
### Why it was tried
- Steel promised full CDP access for richer browser control
- Built-in session viewer and management UI
- Docker-based, clean separation from Hermes host
### Timeline
1. **Jul 29:** Steel deployed on CT201 via Docker Compose, Chromium 140. Hermes configured with `browser.cloud_provider: steel`, `browser-steel` plugin enabled.
2. **Jul 29 (later):** CDP connectivity issues surfaced — Hermes was reaching `0.0.0.0` from the plugin's internal CDP URL. Required `_normalize_cdp_url()` patch in the Steel plugin to remap to `100.96.244.39`.
3. **Jul 30:** DeepSeek V4 Flash 0731 went live and rejected tool names that didn't match `^[a-zA-Z0-9_-]+$`. The Steel plugin's tools (`steel_scrape`, `steel_session_options`) were fine, but the route through OmniRoute → Steel → CDP was unreliable with empty-stream errors.
4. **Jul 30 (evening):** Decision to revert — Camoufox re-enabled, browser-steel plugin disabled, `CAMOFOX_URL` and `CAMOFOX_API_KEY` uncommented in `.env`. Steel left running on CT201 but Hermes no longer routes through it. *(Superseded 2026-10-29 — Steel was removed entirely.)*
### What broke
- CDP URL normalization required a plugin patch to handle Docker's internal networking
- Empty-stream errors from `opencode-go/deepseek-v4-flash` provider path — the combo strategy does NOT iterate on empty responses, they pass to Hermes's own fallback chain (the #1 cause of "combo works but Hermes falls back")
- Tool name validation on DeepSeek 0731 was stricter — this affected all providers, not just Steel
### Lesson learned
Steel is a capable backend but adds a network hop and another plugin layer. Camofox runs locally on the
Hermes host (CT460) with fewer failure modes. Steel was **fully removed on 2026-10-29** — plugin deleted, and
the CT201 and CT333 deployments torn down — so returning to Steel means redeploying it, not flipping a flag.
## Detail
### Camofox (current primary)
- **Deployed:** Persistent `systemd --user` service on the Hermes host (CT460), `camofox-browser.service`
- **Connection:** REST API **and** CDP WebSocket at `localhost:9377`, profile `anthony`, sessionKey `anthony`
- **Limits:** drop-in `MemoryHigh=2G` / `MemoryMax=3G` / `MemorySwapMax=1G` — a 2026-10-12 browser-heavy cron run hit `2.5G` with swap fully consumed and had to be restarted (see [[systems/browser-backend]])
- **Key advantage:** Runs on the same host as Hermes — no network hop, no container networking to debug
- **Auth:** Already authenticated into services (Uber Eats, LinkedIn, etc.) — no cookie files needed
- **Limitation:** Headed via Xvfb, consumes display resources
### Steel Browser (removed 2026-10-29 — no longer available)
- **Deployed:** 2026-07-29 on CT201, Docker, custom `steel-browser-api:fixed` image *(historical)*
- **Status:** **FULLY REMOVED on 2026-10-29** — not merely offline. On CT201 the containers
`steel-browser-api-1` / `steel-browser-ui-1`, the `steel-network` Docker network, the images
(`steel-browser-api:fixed`, `ghcr.io/steel-dev/steel-browser-api:latest`,
`ghcr.io/steel-dev/steel-browser-ui:latest`) and the project dir `/root/steel-browser` were all deleted
(~6 GB reclaimed). The Tailscale Serve routes `/steel` and `/steel-api` were removed, so the former CDP
`:9223`, REST `:3000` and UI `/steel` addresses are all retired — nothing listens on 3000, 5173 or 9223.
- **CT333 copy:** a second, separate Steel install (`steel-browser`, `ghcr.io/steel-dev/steel-browser:latest`)
was also removed with its image. It had been orphaned — no requests since 2026-10-21, and no reference from
Zeroclaw, Nanobot or any Serve route.
- **Plugin:** **deleted 2026-10-29** — `~/.hermes/plugins/browser-steel/` is gone and no `browser-steel` key
remains in `plugins.disabled` / `plugins.entries`, so the `plugin_steel` toolset cannot be selected.
- **Reversibility:** the compose file and Dockerfile are archived on CT201 under `/root/_archived-steel/`, plus
`/root/_archived-steel/steel-cache-archive-20261029.tgz`; the images remain re-pullable from ghcr.io.
## Related
- [[systems/browser-backend]]
- [[concepts/browser-automation]]
- [[decisions/rollback-steel-to-camofox]]