7.8 KiB
7.8 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-09-30 | 2026-09-30 | 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+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 guardhermes-runtime-deps-guard.shverifiesdotenv+mnemosynein every venv every 15 min — see incidents/2026-09-28-hermes-managed-runtime-deps. - Community resources: 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:4000with modelfreellmapi-auto - Provider model count: ~3430 (omniroute), ~1512 (litellm)
- 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: 341 (per stocktake 2026-09-25)
- 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).
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: connected
- 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-09-30
- 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.
- Daily Marketing Job Radar pinned to a model its upstream plan rejects (
gpt-5.6-terra→ 403MODEL_NOT_IN_PLAN). See systems/scheduled-tasks. - Telegram thread delivery failures on
telegram:1793951355(thread34795not found). - 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