Files
agent-estate-wiki/agents/hermes-chaos.md
T

5.6 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Hermes Chaos system active 2026-08-15 2026-11-08 2026-11-08 high
hermes
chaos
ct450
experimental
agent
live-probe
config-inspection

Hermes Chaos

Purpose

Experimental Hermes instance for testing new configurations, skills, themes, model routing, and plugin changes before promoting them to production. Changes here must not affect CT460 production without explicit approval.

Location

  • Container: LXC CT450 (hermesagent)
  • Access: no SSH — go through the PVE host: ssh root@100.96.100.82, then pct exec 450 -- <cmd> (or pct enter 450). hermes is not on pct exec's default PATH; use su - hermes -c "/home/hermes/.local/bin/hermes …".
  • Tailscale IP: 100.98.205.112
  • Hostname: hermesagent
  • Software: hermes-ui (Vite web app for browser use, port 5174)
  • Memory: CPU-only container (no GPU) — self-hosted VRAM models are off the table

Current State

  • Status: Active (experimental)
  • Hermes version: ⚠ now v0.23.0 — the live install stamp ~/.hermes/hermes-agent/install-stamp.json inside CT450 reads baseVersion: 0.23.0, displayVersion: 0.23.0, distance: 0, payload: bootstrap (probed 2026-11-08 00:4x AWST by the nightly audit; hermes --version not re-run in that probe). The rest of this bullet is the 2026-11-07 correction, written when CT450 was still v0.22.5 (2026.9.24), local bf0203a794a0 — the same build as CT460 (updated 2026-10-21). ⚠ Corrected 2026-11-07: this line still read "v0.22.3 … local 5b147ab036d6" while asserting it was "the same build as CT460" — it was not. Live hermes --version on CT450 then returned v0.22.5 … local bf0203a794a0, byte-identical to CT460's own hermes --version, so the same build claim finally became true. hermes update --check then reported stable v0.23.0 (2bd378ed1b8d) available; CT460 took it on 2026-11-07 and CT450's stamp now reads the same version. Python 3.14.9. See incidents/2026-10-03-ct450-hermes-update.
  • Mattermost connection failing: the gateway logs mattermost connect timed out after 30s, next retry in 300s every 5 minutes. Host-side condition (Mattermost unreachable), not a CT450 regression — see systems/messaging-integrations.
  • Soul: Chaos — the unhinged raccoon 🦝 (SOUL.md beat-bank variant, updated 2026-08-01)
  • Cron jobs: 25 — 13 enabled / 12 disabled (verified live in CT450's jobs.json 2026-11-07; unchanged). 9 job names are shared with CT460; 8 of those are disabled here and enabled on CT460, while Important-mail monitor is the reverse (enabled on CT450, disabled on CT460) — both confirmed by a live set-diff of the two jobs.json files on 2026-11-07
  • Production counterparts: CT460 has 28 jobs / 25 enabled — the two fleets no longer share a job count, and the CT450 duplicates are paused

Providers & Routing

  • Default model: smart-route via custom → http://100.78.63.20:20128 (the omni-101 node) — verified live in CT450's config.yaml 2026-10-26. ⚠ The old claim of deepseek-flash-mix on custom:omniroute (100.88.81.19) no longer matches the config
  • Fallback chain (fixed 2026-08-15 — OmniRoute fallback entries removed, they were non-functional):
    1. kilo-stepfun-step-3_7-flash-free via litellm_4000
    2. nvidia/nemotron-3-ultra:free via nous
    3. auto via custom at https://freellmapi.com/v1
  • Important: fallback_providers must stay a YAML list — hermes config set writes strings, which silently disables the whole chain (_iter_fallback_entries returns [] for strings). Edit via the hermes fallback command or direct YAML edit.
  • See systems/model-providers for full breakdown.

Browser & Desktop Access

  • Browser engine: camofox on port 9377 (config: engine: camofox). Does not expose raw CDP on 9222 — do not point cdp_url at 9222 or browser tools fail with connection refused.
  • VNC desktop: camofox-vnc.service (user unit) on Xvfb :127, RFB 5901, localhost-only no-auth. View at hermesagent.kangaroo-eel.ts.net/vnc.html.
  • CDP endpoint for typed-browser ops: bind via cua_browser_prepare/cua_browser_state on the Camofox window; legacy browser_navigate works for plain navigation.
  • See systems/browser-backend for browser architecture.

Web UIs (do not conflate)

  • WebUI: port 8787 (Python/vanilla JS)
  • hermes-ui: port 5174 (Vite/React desktop-style renderer, proxies to gateway 9119)
  • These are separate projects. Deployment of hermes-ui is done via CX-dump + tar through the PVE host.

Phase One Review (2026-08-08)

Phase One seven-day review completed and independently live-verified:

  • CT450 duplicate jobs remained paused with no post-pause execution records
  • CT460 counterparts remain enabled with successful latest runs
  • CT333 schedules remained enabled and healthy
  • Phase Two is ready for consideration but is NOT approved

Key Rules

  • Do not promote changes to production without explicit approval. Chaos is for testing.
  • Duplicate cron jobs are paused. Do not re-enable without approval.
  • Separate state. Memory, skills, and config are independent from CT460.
  • Wiki governance: write only to this section (agents/hermes-chaos.md); never hand-edit auto-generated pages like systems/skills-index.

Relationship to Production

Hermes Chaos (CT450) and Hermes Production (CT460) are separate Hermes instances with:

  • Separate configs
  • Separate skills
  • Separate cron jobs
  • Separate memory state (Chaos runs Hindsight, bank hermes-clean; production runs Mnemosyne)
  • Separate Tailscale