wiki(audit): 2026-10-28 window — radar stage-1 iteration cap (no handoff, stage-2 no-oped), stocktake 400 never alerted, Steel removed from the stack

This commit is contained in:
hermes
2026-10-29 00:41:30 +08:00
parent 2cbf0b65c1
commit ec0c30fb30
12 changed files with 374 additions and 27 deletions
+26 -3
View File
@@ -3,8 +3,8 @@ title: Browser Backend
type: system
status: active
created: 2026-07-22
updated: 2026-10-13
verified_on: 2026-10-13
updated: 2026-10-29
verified_on: 2026-10-29
confidence: high
tags: [browser, camofox, automation]
sources: [live-probe, config, session-history]
@@ -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):** Still running but Hermes not connected — plugin disabled
- **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.
## Camofox (local `systemd --user` service)
@@ -109,6 +109,29 @@ until the next session starts.
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.
## Correction (2026-10-29) — Steel is out of the stack, not just disabled
Verified against live state at **2026-10-29 00:3x AWST**:
- **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.
## Related
- [[comparisons/steel-vs-camoufox]]
- [[concepts/browser-automation]]