Files
agent-estate-wiki/agents/hermes-production.md
T
Tony0410 0b4ff25fd2 resolve: Gitea config backup push dead since 2026-08-08 — 92-commit backlog drained, script hardened to fail loudly
- Wire host-scoped Gitea credential (git credential approve); origin was HTTPS with no userinfo
- Strip 1.76GB checkpoints/ from the unpushed range via git filter-repo --partial (fast-forward preserved)
- Untrack checkpoints/ at the tip; push set ~2GB -> 264.8MB
- Rewrite backup.sh: exit non-zero on failure, stamp .last_backup_ok only after remote verification,
  decide push by remote-vs-local, guard ls-remote with || true, GitHub orphan snapshot via commit-tree,
  honest AgentMail/Telegram delivery reporting
- Verified live: exit 0, origin/main == local HEAD, 0 unpushed, Gitea + GitHub APIs confirmed
- Incident page -> status: resolved; backups.md -> RESOLVED; scheduled-tasks job row updated
- Also commits the uncommitted stocktake edits (the 03:00 stocktake cron failed with
  'lost its durable fire claim ownership' and left the tree dirty)
2026-11-07 05:28:39 +08:00

5.1 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Hermes Production system active 2026-08-15 2026-11-07 2026-11-07 high
hermes
production
ct460
agent
live-probe
config-inspection

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.118.5.51 (⚠ 100.96.100.82 is the PVE hypervisor pve, not CT460 — corrected 2026-10-26)
  • Hostname: hermes
  • Ports: 9119 (gateway/API), 8085 (webhook) — ⚠ the old 8082 claim was dead: no 8082 listener on CT460 as of 2026-10-26
  • Memory: 14GB (upgraded from 5096MB on 2026-08-07)

Current State

  • Status: Active
  • Hermes version: v0.22.3 (2026.9.24), local 5b147ab036d6 — updated 2026-10-21 22:47→22:57 AWST; verified live 2026-10-26. (hermes update --check reports stable v0.22.5 available)
  • Python: managed runtime 3.14 (legacy venv/ on 3.11.15)
  • Install directory: /home/hermes/.hermes/hermes-agent
  • Config: ~/.hermes/config.yaml
  • Profile: default — top-level config; no profiles/default/ directory exists (ops at ~/.hermes/profiles/ops/ is the only named sub-profile)
  • 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:omni-101 → http://100.78.63.20:20128 (OmniRoute node omniroute-1, CT101/m93p) — verified live 2026-10-26, re-verified 2026-11-07 (live config.yaml model.default.provider: custom:omni-101; a keyed deepseek-paid-smart chat probe against 100.78.63.20:20128 returns HTTP 200). The custom:omni provider key does not exist in custom_providers. ⚠ Corrected 2026-11-07: the old claim that "2 cron jobs still pin custom:omni" is no longer true — live jobs.json shows no job pinned to the bare custom:omni; all 21 provider-pinned jobs use custom:omni-101 (see systems/scheduled-tasks)
  • Default model: smart-route (previously freellmapi-auto)
  • Fallback providers (live chain, re-verified 2026-10-26): nous / meituan/longcat-2.5-preview:free → opencode-zen / deepseek-v4.1-flash → custom:guacano / deepseek-v4.1-flash → custom:litellm / kilo-reflection-beam-free → kilocode / poolside/laguna-m.1:free → custom (http://litellm:4000/v1) / or-inclusionai_ling-2_6_1t. ⚠ The first entry is the dead nous credential — a fallover tries it first
  • Auxiliary models: all eight auxiliary: slots (approval, compression, curator, mcp, profile_describer, skills_hub, title_generation, vision) are no-think/freeapi/auto on custom:omni-101 with a freeapi/deepseek-v4-flash → kg/kilo-auto/free fallback chain (moved 2026-10-25 19:13)
  • See systems/model-providers for full breakdown.

Memory

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

Scheduled Tasks

  • Cron jobs: 28 — 25 enabled / 3 disabled (verified live jobs.json 2026-10-26). 5 non-clean last_status: 0e753e9720fd (error), fad5a86979d4 + 066bb5191280 (delivery_failed), 08eb86f02d37 (delivery_queued, empty last_error), c0a9fa314542 (error, streak 1)
  • Delivery targets: Telegram (primary), Discord, origin, local
  • Notable: Birthday checker, job radar, newsletter digests, mnemosyne health/watchdog/backup
  • See systems/scheduled-tasks for full table.

Messaging

  • Telegram, Discord, Slack, Email, Mattermost, ntfy
  • Mattermost is currently unreachable — the gateway logs mattermost connect timed out after 30s, next retry in 300s (re-probed live 2026-10-26) and the Mattermost host does not answer: CT255 is stopped on pve and its Tailscale peer has been offline 36d. Treat Mattermost delivery as down until probed.
  • See systems/messaging-integrations for details.

Key Differences from Chaos

Aspect Production (CT460) Chaos (CT450)
Purpose Stable daily operations Experimental/testing
Cron jobs 29 (26 enabled / 3 disabled) (re-verified 2026-11-07) 25 jobs (13 enabled / 12 disabled), 9 names shared with CT460 (re-verified 2026-11-07)
Config changes Requires verification Safe to experiment
Memory Production Mnemosyne Separate state