wiki audit 2026-10-03: cliprox second job confirmed (2/3), work-mailbox incident page, streak recount, skills-index 341->344
This commit is contained in:
+11
-8
@@ -3,11 +3,11 @@ title: Hermes Agent
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-01
|
||||
verified_on: 2026-10-01
|
||||
updated: 2026-10-03
|
||||
verified_on: 2026-10-03
|
||||
confidence: high
|
||||
tags: [system, hermes, agent, llm]
|
||||
sources: [live-hermes-version, live-config]
|
||||
sources: [live-hermes-version, live-config, live-skill-inventory]
|
||||
---
|
||||
|
||||
# Hermes Agent
|
||||
@@ -74,9 +74,10 @@ Primary personal agent for Anthony. Runs automation, research, communication, kn
|
||||
- See [[terminal-backend]] for details.
|
||||
|
||||
## Skills
|
||||
- **Total installed:** 344 `SKILL.md` files across 72 top-level skill directories (live count, 2026-10-01; the last full stocktake on 2026-09-25 recorded 341)
|
||||
- **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).
|
||||
- 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
|
||||
|
||||
@@ -106,7 +107,7 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi
|
||||
- **Telegram:** enabled, `allowed_chats: -1004321904721,-1003914987043,-1003932503629`, rich messages
|
||||
- **Discord:** enabled, streaming true
|
||||
- **Slack:** enabled
|
||||
- **Email:** connected
|
||||
- **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`)
|
||||
@@ -115,7 +116,8 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi
|
||||
- See [[messaging-integrations]] for details.
|
||||
|
||||
## Scheduled Tasks
|
||||
- **Cron jobs:** 30 total (27 enabled, 3 disabled) — verified 2026-10-01
|
||||
- **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.
|
||||
@@ -129,7 +131,8 @@ The `allowed_chats` gate runs on the **default profile's adapter** before `profi
|
||||
|
||||
## 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]].
|
||||
- **Three cron jobs are pinned to models that no longer exist upstream and cannot self-recover** (`1a8e90ea2271` → `qwen3.5:397b` retired 2026-09-25, HTTP 410; `dca8482e4f76` → `gpt-5.6-terra` plan-gated, 403 `MODEL_NOT_IN_PLAN`; `fad5a86979d4` → `deepseek-v4-flash` absent from the NVIDIA live catalog, HTTP 400). Repinning to the `smart-route` alias is the durable fix. See [[systems/scheduled-tasks]] and [[systems/model-providers]].
|
||||
- **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.
|
||||
|
||||
Reference in New Issue
Block a user