Files
agent-estate-wiki/systems/hermes-agent.md
T

150 lines
10 KiB
Markdown

---
title: Hermes Agent
type: system
status: active
created: 2026-07-22
updated: 2026-10-03
verified_on: 2026-10-03
confidence: high
tags: [system, hermes, agent, llm]
sources: [live-hermes-version, live-config, live-skill-inventory]
---
# Hermes Agent
## Purpose
Primary personal agent for Anthony. Runs automation, research, communication, knowledge management, browser control, and scheduled tasks.
## Current Status
- **Version:** v0.21.5+3837.gbfda74c (2026.9.24), upstream `27062c34` — verified 2026-09-30
- **Install method:** git
- **Python:** 3.11.15
- **Upstream status:** Update available (`hermes update`)
- **Install directory:** `/home/hermes/.hermes/hermes-agent`
- **Managed runtimes:** 10 uv-managed venvs under `~/.hermes/installs/019d0d114d22b7e6/environments/<hash>/venv`. Dependency guard `hermes-runtime-deps-guard.sh` verifies `dotenv` + `mnemosyne` in every venv every 15 min — see [[incidents/2026-09-28-hermes-managed-runtime-deps]].
- **Community resources:** [Hermes Registry](https://babylondreams.de/hermes-registry/) — third-party plugins, skills, and extensions
- **Binary:** `/home/hermes/.local/bin/hermes`
- **Config:** `~/.hermes/config.yaml`
- **Profile:** `default` (`~/.hermes/profiles/default/`)
## Location
- **Host:** Local Linux host (no containerized Hermes runtime confirmed)
- **Filesystem root:** `~/.hermes/`
- **Working directory:** `/home/hermes/workspace`
## Providers & Routing
- **Default provider:** `custom` → `http://100.78.63.20:20128` (OmniRoute) — verified 2026-09-30
- **Default model:** `smart-route` — verified 2026-09-30
- **History:** as at 2026-07-22 this was `custom:litellm` → `litellm:4000` with model `freellmapi-auto`
- **Provider model count (2026-10-01):** 5 custom providers — `omni-101` 5,384, `Omniroute:20128` 5,398, `litellm` 1,728, `command-code` 71, `guacano` 46
- **MCP servers:** 5 configured (`Not human search`, `asana`, `cua-driver`, `hound`, `mcp-portal`) — verified 2026-10-01
- **Plugins enabled:** 11 — verified 2026-10-01
- **free-stack combo (OmniRoute):** Nemotron 3 Ultra 550B configured with `max_tokens: 8192`, `reasoning_effort: medium`, `chat_template_kwargs.force_nonempty_content: true` (see [[omniroute]])
- See [[model-providers]] for full breakdown.
## Memory
- **Backend:** Mnemosyne (local native)
- **Memory enabled:** true
- **Char limit:** 5000
- **User profile enabled:** true
- **User char limit:** 3000
- **Flush every:** 6 turns
- **Auto sleep:** true
- **Default scope:** session
- **Vector type:** int8
- **Shared surface:** `data/shared/mnemosyne.db`
- See [[memory-backend]] for details.
## Browser
- **Cloud provider:** Camoufox
- **Managed persistence:** true
- **Inactivity timeout:** 120 s
- **Allow private URLs:** true
- **cua-driver:** v0.9.0 at `/home/hermes/.cua-driver/packages/releases/0.9.0-x86_64-unknown-linux-gnu/cua-driver`
- **DISPLAY:** `:102` (Xvfb/X11VNC/fluxbox confirmed working per session notes)
- See [[browser-backend]] for details.
## Terminal
- **Backend:** local
- **Working directory:** `/home/hermes/workspace`
- **Timeout:** 180 s
- **Home mode:** auto
- **Container CPU:** 1
- **Persistent shell:** true
- See [[terminal-backend]] for details.
## Skills
- **Total installed:** 344 `SKILL.md` files across 72 top-level skill directories (live count 2026-10-03; re-confirmed by the manual stocktake the same day — the last generated [[skills-index]] also reads 344 / 70 categories)
- Newest addition: `fleet-wide-failure-triage` (devops) — surfaced by the 2026-10-03 regeneration
- Key skills: hermes, hermes-gateway-troubleshooting, hermes-mcp-troubleshooting, hermes-api-vault, omniroute, job-search-automation, weekly-review, fresh-rss-intelligence-filter, etc.
- See [[skills-index]] for categorized list (auto-regenerated daily — but the generating job is currently blocked, so it is being refreshed by hand; see Known Issues).
## Multi-Profile Multiplexer
The default gateway runs as a **profile multiplexer** (`gateway.multiplex_profiles: true`), serving both the `default` and `ops` profiles through a single gateway process with one Telegram connection.
### Profiles
| Profile | Chat | Purpose |
|---------|------|---------|
| default | `-1004321904721` (Rhino chat) | Main agent |
| ops | `-1003914987043` (Elephant ops), `-1003932503629` (OPS Tember rescue) | Operations/infra agent |
### How It Works
- **One gateway, one Telegram bot token** — shared across profiles
- **`profile_routes`** maps chat_id → profile at the gateway level
- **`allowed_chats` on both profiles** must include ALL chats that either profile should hear, because the default profile's adapter processes all inbound messages before `profile_routes` stamps `source.profile`
- The ops profile does NOT need `platforms.telegram.enabled` — the default adapter handles it
### Critical Rule: allowed_chats Is Pre-Route
The `allowed_chats` gate runs on the **default profile's adapter** before `profile_routes` matching. If a chat_id is only in the ops profile's `allowed_chats` but not the default's, messages from that chat are silently dropped before routing ever fires.
**Fix applied 2026-07-28:** Added both ops group IDs to the default profile's `allowed_chats` and `group_allowed_chats` (comma-separated). See [[multiplexer-setup]].
## Messaging Integrations
- **Telegram:** enabled, `allowed_chats: -1004321904721,-1003914987043,-1003932503629`, rich messages
- **Discord:** enabled, streaming true
- **Slack:** enabled
- **Email:** ⚠ partially connected — personal Gmail works; the `work` Outlook account is unreachable (tenant allows only `XOAuth2`, the account uses password auth). See [[incidents/2026-08-26-work-outlook-basic-auth-disabled]].
- **Mattermost:** connected; gateway warning on 2026-08-15 was caused by a disabled system-level `hermes-gateway.service` unit, not a live duplicate gateway. Only the user-level service is active.
- **ntfy:** connected
- **Google Chat:** available (`hermes-google_chat`)
- **QQ:** available (`hermes-qqbot`)
- **Yuanbao:** available
- See [[messaging-integrations]] for details.
## Scheduled Tasks
- **Cron jobs:** 30 total (27 enabled, 3 disabled) — verified 2026-10-03
- **Failing: 6** — `dca8482e4f76` (403 plan-gated), `1a8e90ea2271` (HTTP 410, retired model), `fad5a86979d4` (HTTP 400), `0e753e9720fd` (HTTP 400), `06a0a1c8704f` and `1b23c042e17d` (HTTP 401 — the `cliprox/terra` provider connection auth expired, now confirmed on 2 of the 3 jobs sharing that pin)
- Delivery targets: Telegram (primary), Discord, origin, local
- Notable: Birthday checker, job radar, newsletter digests, GitHub trending, mnemosyne health/watchdog/backup, AgentMail watcher, skills stock-take regeneration
- See [[scheduled-tasks]] for full table.
## Dependencies
- LiteLLM proxy at `litellm:4000`
- OmniRoute at `omniroute:20128`
- cua-driver binary at path above
- Xvfb + X11VNC + fluxbox for headed browser
- Telegram bot token, Discord token, etc. (stored outside wiki)
## Known Issues
- Managed-runtime venvs previously drifted on dependencies, breaking cron workers — now guarded every 15 min. See [[incidents/2026-09-28-hermes-managed-runtime-deps]].
- **Four cron jobs cannot self-recover — three pinned to models that no longer exist upstream, plus a credential fault:** `1a8e90ea2271` → `qwen3.5:397b` retired 2026-09-25 (HTTP 410); `dca8482e4f76` → `gpt-5.6-terra` plan-gated (403 `MODEL_NOT_IN_PLAN`); `fad5a86979d4` + `0e753e9720fd` → `deepseek-v4-flash` absent from the NVIDIA live catalog (HTTP 400); and `06a0a1c8704f` + `1b23c042e17d` → the `cliprox/terra` provider *connection* auth expired (HTTP 401), now confirmed on 2 of the 3 jobs sharing that pin. Repinning to the `smart-route` alias is the durable fix for the model faults; the cliprox pair needs the OmniRoute connection re-authenticated first. See [[systems/scheduled-tasks]], [[systems/model-providers]] and [[incidents/2026-10-01-cliproxy-connection-auth-expired]].
- **The daily skills stock-take is not running.** Job `1a8e90ea2271` is blocked on the retired model above, so [[skills-index]] and the freshness audit are only refreshed when `wiki-maintain.sh` is run by hand (last done 2026-10-03). The script itself is healthy — only the scheduled wrapper is broken.
- **Telegram thread delivery failures — root-caused and fixed 2026-09-30.** A bare `deliver: "telegram"` resolves to the home DM (`1793951355`), where group forum topic IDs cannot exist; the send hard-failed and the message was lost. Two jobs were retargeted to `telegram:-1004321904721:102` and verified. Three jobs still use bare `telegram` targets. See [[systems/messaging-integrations]].
- **Two wiki trees drift:** `/home/hermes/workspace/agent-estate-wiki` (Gitea + Quartz source, pages at root) and `/home/hermes/wiki/agent-estate-wiki` (Obsidian/Ignis vault, pages under `wiki/`). They are separate git repos with different history. See [[current-state]].
- **Vault repo git objects can be unwritable:** `/home/hermes/wiki/.git` still holds root-owned object fanout dirs/objects (`04`, `42`, `82`, `91`) left by root-run maintenance commits on 2026-07-22. When a new blob or tree hashes into one of those fanouts, `git commit` dies with `insufficient permission for adding an object to repository database` (even though `git add`/`write-tree` look fine). Workaround that works: build the objects in a writable store via `GIT_OBJECT_DIRECTORY=<tmp>` + `GIT_ALTERNATE_OBJECT_DIRECTORIES=/home/hermes/wiki/.git/objects`, then `git pack-objects /home/hermes/wiki/.git/objects/pack/pack-<name>` and move the branch with `git update-ref refs/heads/master <commit>`. Permanent fix is a root `chown -R hermes:hermes /home/hermes/wiki/.git`. Do **not** run overwrite/rename probes against `.git/objects`: on 2026-09-30 one such probe overwrote loose tree `0d23eba37eb65f5e5021f558a370358f1e394c58` (breaking the 2026-07-22 commit `9141a88`); it was reconstructed byte-exactly from its parent tree `d8185c99` plus the two replaced children (`comparisons` tree `822b90a7`, `log.md` blob `043dc1cd`) and reinserted, and `git fsck` is clean again.
- Browser persistence not yet fully verified
## Related
- [[model-providers]]
- [[memory-backend]]
- [[browser-backend]]
- [[terminal-backend]]
- [[skills-index]]
- [[messaging-integrations]]
- [[scheduled-tasks]]
- [[current-state]]