11 KiB
11 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hermes Agent | system | active | 2026-07-22 | 2026-10-04 | 2026-10-04 | high |
|
|
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+6169.gab86a20 (2026.9.24), upstream
ab86a20a— verified live 2026-10-04. Same semver token as the earlierv0.21.5+3837.gbfda74c(27062c34), but a newer build: the install tree was rebuilt 2026-10-03 10:11 AWST. - Install method: git
- Python: managed runtime 3.14 (legacy
venv/on 3.11.15) - Upstream status: tree rebuilt 2026-10-03 from upstream
ab86a20a; update availability not re-checked since. - Install directory:
/home/hermes/.hermes/hermes-agent - Managed runtimes: 3 uv-managed venvs under
~/.hermes/installs/019d0d114d22b7e6/environments/<hash>/venv(was 10 — the 2026-10-03 rebuild pruned superseded environments and created two new ones at 09:59/10:00; the third survives from 2026-09-28).hermes-runtime-deps-guard.shruns every 15 min viamnemosyne-watchdog.pyand now assertsdotenv+mnemosynein the installer python and every managed venv, plusfastembed+FASTEMBED_CACHE_PATH+ the local model dir in the bootstrap-selected venv — see incidents/2026-09-28-hermes-managed-runtime-deps and incidents/2026-10-03-mnemosyne-vector-recall-fts-only. - Community resources: Hermes Registry — third-party plugins, skills, and extensions
- Binary:
/home/hermes/.local/bin/hermes - Config:
~/.hermes/config.yaml - Profile:
default(top-level config~/.hermes/config.yaml; the only named sub-profile on this host isopsat~/.hermes/profiles/ops/)
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:4000with modelfreellmapi-auto - Provider model count (2026-10-01): 5 custom providers —
omni-1015,384,Omniroute:201285,398,litellm1,728,command-code71,guacano46 - 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.mdfiles 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_routesmaps chat_id → profile at the gateway levelallowed_chatson both profiles must include ALL chats that either profile should hear, because the default profile's adapter processes all inbound messages beforeprofile_routesstampssource.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
workOutlook account is unreachable (tenant allows onlyXOAuth2, 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.serviceunit, 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),06a0a1c8704fand1b23c042e17d(HTTP 401 — thecliprox/terraprovider 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.
- Vector recall silently ran keyword-only until 2026-10-03 (repaired).
fastembedwas missing from every uv-managed runtime andFASTEMBED_CACHE_PATHwas unset, so the dense leg ofmnemosyne_recallreturned no candidates and recall degraded to FTS5 — with no error raised. Repaired 2026-10-03 and the guard extended (above). Live coverage 2026-10-04: working 726/752 (96.5%), episodic 1033/1039 (99.4%). See incidents/2026-10-03-mnemosyne-vector-recall-fts-only. - Four cron jobs cannot self-recover — three pinned to models that no longer exist upstream, plus a credential fault:
1a8e90ea2271→qwen3.5:397bretired 2026-09-25 (HTTP 410);dca8482e4f76→gpt-5.6-terraplan-gated (403MODEL_NOT_IN_PLAN);fad5a86979d4+0e753e9720fd→deepseek-v4-flashabsent from the NVIDIA live catalog (HTTP 400); and06a0a1c8704f+1b23c042e17d→ thecliprox/terraprovider connection auth expired (HTTP 401), now confirmed on 2 of the 3 jobs sharing that pin. Repinning to thesmart-routealias 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
1a8e90ea2271is blocked on the retired model above, so skills-index and the freshness audit are only refreshed whenwiki-maintain.shis 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 totelegram:-1004321904721:102and verified. Three jobs still use baretelegramtargets. 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 underwiki/). They are separate git repos with different history. See current-state. - Vault repo git objects can be unwritable:
/home/hermes/wiki/.gitstill 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 commitdies withinsufficient permission for adding an object to repository database(even thoughgit add/write-treelook fine). Workaround that works: build the objects in a writable store viaGIT_OBJECT_DIRECTORY=<tmp>+GIT_ALTERNATE_OBJECT_DIRECTORIES=/home/hermes/wiki/.git/objects, thengit pack-objects /home/hermes/wiki/.git/objects/pack/pack-<name>and move the branch withgit update-ref refs/heads/master <commit>. Permanent fix is a rootchown -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 tree0d23eba37eb65f5e5021f558a370358f1e394c58(breaking the 2026-07-22 commit9141a88); it was reconstructed byte-exactly from its parent treed8185c99plus the two replaced children (comparisonstree822b90a7,log.mdblob043dc1cd) and reinserted, andgit fsckis clean again. - Browser persistence not yet fully verified