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)
• Tailscale IP: 100.98.205.112
• Hostname: hermesagent
• Software: przbadu/hermes-ui (Vite web app for browser use)

Current State

• Status: Active (experimental)
• Hermes UI: przbadu/hermes-ui running on CT450
• Duplicate cron jobs: 11 paused (no post-pause execution records since 2026-08-01)
• Production counterparts: CT460 has 11 enabled jobs with successful latest runs

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.

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
• Separate Tailscale identities

Related

• hermes-production — The production instance
• hosts — Host inventory
• hermes-agent — Hermes Agent system details