Browser Backend

Purpose

Browser automation for Hermes — web search, form filling, screenshot, CDP control, authenticated scraping.

Primary backend: Camoufox (Firefox-based, anti-fingerprint) on CT450
Provider config: browser.cloud_provider: camofox, camera_provider: camofox
REST API: localhost:9093 (profile anthony, sessionKey anthony)
CDP WebSocket: localhost:9377 (via Camoufox’s Playwright bridge)
VNC viewer: https://ct460.kangaroo-eel.ts.net/vnc-camofox (port 6080)
Steel Browser (CT201): Still running but Hermes not connected — plugin disabled

Host: CT450 (same host as Hermes — no network hop)
Deployment: Systemd service camofox-browser.service
Engine: Camoufox (custom Firefox build with anti-detection fingerprinting)
Display: Headed via Xvfb :99 (1600×1200×24) + fluxbox window manager
Auth: Persistent profile anthony — authenticated into Uber Eats, LinkedIn, etc.
Connection: REST API at localhost:9093 for session management, CDP WebSocket at localhost:9377 for browser tools
Last verified: Jul 30 — browserConnected: true, sessions: 1, tabs: 1, active 200s on scroll/navigate

Endpoint	URL	Used by
REST API	`http://localhost:9093`	Hermes browser tools (navigate, click, snapshot)
CDP WebSocket	`ws://localhost:9377`	Direct CDP control
VNC	`https://ct460.kangaroo-eel.ts.net/vnc-camofox`	Visual session viewer
Camoufox UI	`http://localhost:9378`	Internal management

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
See: steel-vs-camoufox for the full experiment story

2026-07-22: Camoufox primary, cua-driver bridge
2026-07-29: Steel Browser deployed on CT201, became primary
2026-07-30: Steel reverted — CDP issues + DeepSeek 0731 tool name validation problems. Camoufox restored as primary.
2026-08-02: Camoufox confirmed working with authenticated sessions (Uber Eats report via Camofox REST API)