4.7 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Rollback Steel to Camoufox | decision | active | 2026-08-02 | 2026-10-29 | 2026-10-29 | high |
|
|
Decision: Rollback Steel Browser → Camoufox
Date
2026-07-30
Context
Steel Browser was deployed on CT201 on 2026-07-29 as the primary browser automation backend, replacing Camoufox. It ran for approximately 24 hours before being reverted.
Options Considered
| Option | Pros | Cons |
|---|---|---|
| Keep Steel | Full CDP access, session viewer UI, Docker isolation | CDP URL normalization issues, network hop, empty-stream errors |
| Revert to Camoufox | Local (no network hop), already authenticated, fewer failure modes | Headed display consumes resources, no built-in session viewer |
| Both (Steel primary, Camoufox fallback) | Redundancy | Complexity, two backends to maintain, unclear which one Hermes uses per-request |
Decision
Revert to Camoufox as primary. Steel plugin disabled but left running on CT201.
Status check 2026-10-20 — the decision is partially undone in configuration. The live
browser:block in~/.hermes/config.yamlreadscloud_provider: steelwithengine: camofox. The engine is Camoufox (decision honoured), but the cloud_provider key still sayssteel, andcamera_provider: camofox. This is the same split seen in comparisons/camoufox-vs-chrome.Meanwhile the Steel service itself is not reachable:
http://steel.martinwa.orgreturns 000 (connection failed) on 2026-10-20. Combined with the degraded CT201 stack recorded in systems/homepage-dashboard (main container removed, asset proxy 502), it looks like the "left running on CT201" part of this decision is no longer true.Recommendation, not actioned here: the
cloud_provider: steelvalue appears to be residue from the reverted deployment. Confirm against the live Steel service and either restore it or setcloud_provider: camofoxso the config matches the decision this page records.
Rationale
- Reliability: Camoufox runs on the same host as Hermes (CT450) — no Docker networking, no CDP URL normalization patches, no container-to-host routing issues.
- Auth persistence: Camoufox's persistent profile
anthonyis already authenticated into key services (Uber Eats, LinkedIn). Steel required cookie re-exports. - Failure mode: The
opencode-go/deepseek-v4-flashempty-stream errors were hitting all providers, but Steel added an extra failure surface (CDP connection, plugin layer) on top of the same problem. - DeepSeek 0731 compatibility: The new model's stricter tool name validation (
^[a-zA-Z0-9_-]+$) affected all providers — not a Steel-specific issue, but another reason to minimise the toolchain.
Consequences
- Positive: Browser automation is stable again. Uber Eats report ran successfully via Camofox on 2026-08-01.
- Negative: Steel's session viewer UI and full CDP access are no longer available to Hermes.
- Neutral: Steel still runs on CT201 — can be re-enabled by uncommenting
.envlines and enabling the plugin.
Evidence
- Camoufox verified working Jul 30:
browserConnected: true,sessions: 1,tabs: 1, active 200s - Uber Eats report (Aug 1) successfully scraped via Camofox REST API — 11 orders, $264.51
- Steel plugin
browser-steelstill present at/home/hermes/.hermes/plugins/browser-steel/— disabled
Update (2026-10-29) — the plugin was removed and the endpoint went dark
The 2026-07-30 rollback disabled the Steel plugin but left it on disk and left Steel running. Both of those
were closed on 2026-10-28 22:00 – 2026-10-29 00:15: browser.cloud_provider / camera_provider were
returned to camofox (backups config.yaml.bak-pre-cloudprovider-fix-20261028T220057Z,
config.yaml.bak-pre-steel-plugin-removal-20261028T161324Z), and ~/.hermes/plugins/browser-steel/ was
removed, so the plugin_steel toolset is no longer selectable.
Steel itself is not serving: CDP :9223 and REST :3000 on 100.96.244.39 refuse, the tunnel route
/steel returns 502, and steel.martinwa.org does not resolve, while the host still answers ping.
STEEL_BASE_URL=http://100.96.244.39:3000 remains exported in 10 live Hermes processes and clears on the next
gateway restart. The decision below is unchanged — Camofox is the backend — but there is now no Steel plugin
fallback in the tree, so returning to Steel would mean redeploying it. Detail:
systems/browser-backend, comparisons/steel-vs-camoufox.