audit(2026-10-13): 10-12 clean (174/0, 3rd day) but GitHub Trending Radar token DEAD (getMe 401) - supersedes the wrong 2026-10-06 'refuted' entry

Incidents 5->2 (deepseek-v4-flash pair closed 03:05:39, Job Radar timeout 07:33:41); storm page re-tallied 11/12 closed with closure timeline.

NEW: Camofox hit its cgroup ceiling inside the 07:01 Job Radar run (2.5G, swap exhausted, 383 tasks) - containment drop-in documented; browser-backend/steel-vs-camoufox/browser-automation corrected to REST :9377 on CT460 (was :9093 on CT450).

Mnemosyne 96.7%/99.4% coverage green; 18 cron sessions, 0 interactive; retention floor 2026-10-07.
This commit is contained in:
hermes-audit
2026-10-13 00:19:15 +08:00
parent 0eee5f101e
commit ebf57146f1
10 changed files with 304 additions and 65 deletions
+11 -9
View File
@@ -3,8 +3,8 @@ title: Steel Browser vs Camoufox
type: comparison
status: active
created: 2026-07-29
updated: 2026-08-02
verified_on: 2026-08-02
updated: 2026-10-13
verified_on: 2026-10-13
confidence: high
tags: [comparison, browser, steel, camofox, decision]
sources: [live-probe, session-history]
@@ -16,14 +16,14 @@ sources: [live-probe, session-history]
Compare the two browser-automation backends available to Hermes, including the Jul 29–30 experiment and the decision to revert.
## At a glance
| | Steel Browser (CT201) | Camoufox (CT450) |
| | Steel Browser (CT201) | Camofox (systemd --user on CT460) |
|---|---|---|
| **In use** | Disabled since 2026-07-30 | **Yes** — primary backend |
| **Engine** | Chromium 140 (Playwright) | Camoufox (Firefox-based) |
| **Connection** | CDP (`ws://` via port 9223) | REST API (localhost:9093) |
| **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 | Systemd service on CT450 |
| **Container** | Docker on CT201 | `systemd --user` unit on the Hermes host (CT460) |
| **Stealth** | Standard Chromium | Anti-detection fingerprinting |
| **Session viewer** | Built-in UI at `/steel` | VNC at `/vnc-camofox` |
| **Plugin** | `browser-steel` plugin (disabled) | Native Hermes `browser.cloud_provider: camofox` |
@@ -47,13 +47,15 @@ Compare the two browser-automation backends available to Hermes, including the J
- 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. Camoufox runs locally on CT450 with fewer failure modes. The `browser-steel` plugin still exists (disabled) if needed in future.
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. The `browser-steel` plugin still exists (disabled) if needed in future.
## Detail
### Camoufox (current primary)
- **Deployed:** Persistent systemd service on CT450
- **Connection:** REST API at `localhost:9093`, profile `anthony`, sessionKey `anthony`
### 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