Hermes Production

Purpose

Primary personal agent for Anthony. Runs automation, research, communication, knowledge management, browser control, and scheduled tasks. This is the production instance — changes here affect live workflows.

Location

Container: LXC CT460 (hermes)
Tailscale IP: 100.96.100.82
Hostname: hermes
Port: 8082 (HTTP), 9119 (gateway)
Memory: 14GB (upgraded from 5096MB on 2026-08-07)

Current State

Status: Active
Hermes version: v0.19.0
Python: 3.11.15
Install directory: /home/hermes/.hermes/hermes-agent
Config: ~/.hermes/config.yaml
Profile: default (~/.hermes/profiles/default/)
Soul: Rhino — trickster-mentor in a green jacket 🎩

Profiles

Profile	Telegram Chats	Purpose
default	`-1004321904721` (Rhino chat)	Main agent
ops	`-1003914987043` (Elephant ops), `-1003932503629` (OPS Tember rescue)	Operations/infra agent (Tusk)

Providers & Routing

Default provider: custom:litellm → http://litellm:4000/v1
Fallback provider: custom:omniroute → http://omniroute:20128/v1
Default model: freellmapi-auto
See model-providers for full breakdown.

Memory

Backend: Mnemosyne (local native)
Vector type: int8
Shared surface: data/shared/mnemosyne.db
See memory-backend for details.

Scheduled Tasks

Cron jobs: 25+ active jobs
Delivery targets: Telegram (primary), Discord, origin, local
Notable: Birthday checker, job radar, newsletter digests, mnemosyne health/watchdog/backup
See scheduled-tasks for full table.

Messaging

Telegram, Discord, Slack, Email, Mattermost, ntfy
See messaging-integrations for details.

Key Differences from Chaos

Aspect	Production (CT460)	Chaos (CT450)
Purpose	Stable daily operations	Experimental/testing
Cron jobs	25+ enabled	11 paused duplicates
Config changes	Requires verification	Safe to experiment
Memory	Production Mnemosyne	Separate state

hermes-chaos — The experimental twin
nanobot — Scout agent on CT333
hermes-agent — Hermes Agent system details
current-profile — Active profile details
hosts — Host inventory