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>
This commit is contained in:
+43
-26
@@ -20,7 +20,7 @@ Browser automation for Hermes — web search, form filling, screenshot, CDP cont
|
||||
- **Provider config:** `browser.cloud_provider: camofox`, `camera_provider: camofox`
|
||||
- **REST API:** **`:9377`** — live-verified 2026-10-13 (`node server.js`, `CAMOFOX_PORT=9377`; `LISTEN *:9377`). **The `:9093` figure in earlier revisions of this page is stale** — nothing was listening on 9093 on 2026-10-13.
|
||||
- **VNC viewer:** NovNC `websockify` on `127.0.0.1:6080` → `127.0.0.1:5900`, published as `https://ct460.kangaroo-eel.ts.net/vnc-camofox`
|
||||
- **Steel Browser (CT201):** **Not reachable as of 2026-10-29 00:3x** — host answers ping (2.5 ms) but CDP `:9223` and REST `:3000` refuse; plugin removed. See the 2026-10-29 correction below.
|
||||
- **Steel Browser (CT201):** **Fully removed on 2026-10-29** — plugin deleted, CT201 deployment torn down, Serve routes deleted. **Camofox is the sole backend.** See the 2026-10-29 correction below.
|
||||
|
||||
## Camofox (local `systemd --user` service)
|
||||
|
||||
@@ -87,12 +87,11 @@ Restart (`systemctl --user restart camofox-browser.service`) is measurable rough
|
||||
baseline: `Memory: 16.5M` cgroup, `peak: 1.4G`, `swap peak: 234.5M`, 16 tasks, `browserConnected: false`
|
||||
until the next session starts.
|
||||
|
||||
## Steel Browser (CT201) — Disabled
|
||||
- **Status:** Still running on CT201, Hermes not connected since 2026-07-30
|
||||
- **Plugin:** `browser-steel` at `/home/hermes/.hermes/plugins/browser-steel/` — disabled
|
||||
- **CDP:** `http://100.96.244.39:9223`
|
||||
- **REST API:** `http://100.96.244.39:3000`
|
||||
- **UI:** `https://runtipi.kangaroo-eel.ts.net/steel`
|
||||
## Steel Browser (CT201) — Removed (2026-10-29)
|
||||
- **Status:** **Fully removed.** Nothing Steel-related survives on CT201 or CT333 — containers, images, network, project dir and Serve routes are all gone. Camofox is the only browser backend.
|
||||
- **Plugin:** `browser-steel` — **deleted** (`~/.hermes/plugins/browser-steel/` no longer exists; no `browser-steel` key in `plugins.disabled` or `plugins.entries`)
|
||||
- **CDP / REST / UI:** **retired** — the former CDP `:9223`, REST `:3000` and `/steel` UI addresses no longer serve anything
|
||||
- **Reversibility:** the compose file and Dockerfile are archived on CT201 under `/root/_archived-steel/`, and the images remain re-pullable from ghcr.io
|
||||
- **See:** [[comparisons/steel-vs-camoufox]] for the full experiment story
|
||||
|
||||
## History
|
||||
@@ -108,29 +107,47 @@ until the next session starts.
|
||||
"Camoufox UI") does not exist; `CT450` host attribution replaced with the local `systemd --user` unit on
|
||||
the Hermes host (CT460). Containment drop-in documented. Same day, the 07:01 Job Radar session was audited
|
||||
end-to-end and its memory-pressure evidence added above.
|
||||
- **2026-10-29 — Steel fully removed.** Config back to `cloud_provider: camofox` / `camera_provider: camofox`,
|
||||
the `browser-steel` plugin deleted, `STEEL_BASE_URL` dropped from `~/.hermes/.env`, and the Steel deployments
|
||||
on **CT201** (containers, images, network, project dir, Serve routes) and **CT333** (container + image)
|
||||
torn down. Camofox is the sole backend.
|
||||
|
||||
## Correction (2026-10-29) — Steel is out of the stack, not just disabled
|
||||
|
||||
Verified against live state at **2026-10-29 00:3x AWST**:
|
||||
Verified against live state at **2026-10-29**. The earlier 00:3x probe said only "not reachable"; the truth is
|
||||
stronger — Steel is **fully removed**, not merely down:
|
||||
|
||||
- **Hermes is back on Camofox.** `config.yaml` (mtime **2026-10-29 00:15:13**) reads
|
||||
`browser.cloud_provider: camofox`, `browser.camera_provider: camofox`, `engine: auto`, `cdp_url: ""`.
|
||||
- **The `browser-steel` plugin is gone** — `~/.hermes/plugins/browser-steel/` no longer exists and
|
||||
`plugins.enabled` carries no steel entry, so the `plugin_steel` toolset cannot be selected. Backup taken
|
||||
immediately before the change: `config.yaml.bak-pre-steel-plugin-removal-20261028T161324Z` (written
|
||||
**2026-10-29 00:13:24**). A second backup, `config.yaml.bak-pre-cloudprovider-fix-20261028T220057Z`, records
|
||||
the 2026-10-28 22:00 attempt.
|
||||
- **The Steel endpoint is not serving.** `ping 100.96.244.39` (runtipi/CT201) answers **2.5 ms**, but
|
||||
`http://100.96.244.39:9223/json/version` (CDP) and `http://100.96.244.39:3000/v1/health` (REST) both return
|
||||
**000** — as does the LAN address `192.168.178.77:9223`. The tunnel route
|
||||
`https://runtipi.kangaroo-eel.ts.net/steel` returns **502**, and `steel.martinwa.org` no longer resolves.
|
||||
Earlier pages describing Steel as "still running on CT201" are superseded by this probe.
|
||||
- ⚠ **Stale environment variable still exported:** `STEEL_BASE_URL=http://100.96.244.39:3000` is present in
|
||||
**10 live Hermes processes** — the gateway tree (`3371780`, `3372125`, `3372912`, `3844013`, `3880214`,
|
||||
`3880663`), `agent-browser` 0.26.0 (`3843841`), two chromium crashpad handlers (`3843878`, `3843880`) and
|
||||
`agentmail-webhook.py` (`402`). It now points at a dead endpoint and clears only when the gateway is
|
||||
restarted. The config is explicit (`cloud_provider: camofox`), so it does not currently misroute browser
|
||||
calls — but it is a trap for anything that reads the variable.
|
||||
- **Hermes is back on Camofox, and Camofox is the sole backend.** The `browser:` block in
|
||||
`~/.hermes/config.yaml` reads exactly `cloud_provider: camofox`, `camera_provider: camofox`, `engine: auto`,
|
||||
`cdp_url: ""`.
|
||||
- **The `browser-steel` plugin is deleted** — `~/.hermes/plugins/browser-steel/` no longer exists, and
|
||||
`plugins.disabled` / `plugins.entries` carry no `browser-steel` key, so the `plugin_steel` toolset cannot be
|
||||
selected. Hermes core source contains **zero** Steel references, so there is no Steel fallback path in the
|
||||
tree. Backups: `config.yaml.bak-pre-steel-plugin-removal-20261028T161324Z`,
|
||||
`config.yaml.bak-pre-cloudprovider-fix-20261028T220057Z`.
|
||||
- **CT201 is clean.** The containers `steel-browser-api-1` and `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 removed
|
||||
(~6 GB reclaimed; disk 70G used → 64G used). The Tailscale Serve routes `/steel` and `/steel-api` were
|
||||
deleted with `tailscale serve --set-path <path> off`; CT201's remaining routes are only `/` → `127.0.0.1:8085`
|
||||
and `/mgr` → `127.0.0.1:8084`, on **both** `:443` and `:8443`. No listeners remain on 3000, 5173 or 9223.
|
||||
- **CT333's second, separate Steel copy is gone too.** The orphaned `steel-browser` container (image
|
||||
`ghcr.io/steel-dev/steel-browser:latest`, 5.53 GB, created 2026-05-30, publishing port 3000) and its image
|
||||
were removed; no Steel containers, images or listeners remain on CT333.
|
||||
- **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.
|
||||
- **Camofox is healthy and working** — REST `http://100.118.5.51:9377` (and `http://localhost:9377`);
|
||||
`/health` returns **200**, `/tabs` returns `{"running":true,"tabs":[]}`.
|
||||
- **Stale environment variable — now cleared from the gateway.** `STEEL_BASE_URL` is no longer in
|
||||
`~/.hermes/.env`. It survived in the environment of already-running processes (inherited at spawn), so the
|
||||
**gateway was restarted on 2026-10-29 01:21 AWST** to clear it: the new gateway tree (PID `3913841`) reads
|
||||
`STEEL_BASE_URL=0`. A few older, unrelated services still carry the variable in their inherited
|
||||
environment (the dashboard unit and `agentmail-webhook.service`) — **no core Hermes code reads
|
||||
`STEEL_BASE_URL`**, so it is inert either way, and it is a runtime-only leftover, **not** a config value.
|
||||
|
||||
> ⚠ **Superseded (the 2026-10-29 00:3x probe):** an earlier version of this correction described Steel as
|
||||
> merely "not reachable — endpoint dark, still running on CT201". That is outdated: Steel is now **removed**,
|
||||
> not down.
|
||||
|
||||
## Related
|
||||
- [[comparisons/steel-vs-camoufox]]
|
||||
|
||||
Reference in New Issue
Block a user