Wiki audit 2026-09-30: managed-runtime dependency incident, cron fleet reconciliation, provider/model refresh
This commit is contained in:
@@ -14,10 +14,10 @@ sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
|
||||
## Telegram
|
||||
- **Status:** enabled, active
|
||||
- **allowed_chats:** `-1004321904721` (primary)
|
||||
- **allowed_chats:** `-1004321904721` (primary), `1793951355` (DM), plus the remaining chat IDs required by both multiplexed profiles on the default adapter — verified 2026-09-30
|
||||
- **Rich messages:** true
|
||||
- **Platform toolsets:** cli, telegram (full suite)
|
||||
- **Delivery targets seen in cron:** telegram, `telegram:1793951355`, `telegram:-1004321904721:1030`, `telegram:-1004321907D2:346`, `telegram:-1004321904721:273`
|
||||
- **Delivery targets seen in cron:** telegram, `telegram:1793951355`, `telegram:-1004321904721`, `telegram:-1004321904721:notifications`, `telegram:-1004321904721:102`, `telegram:-1004321904721:273`, `telegram:-1004321904721:346`, `telegram:-1004321904721:1030`
|
||||
- **Notes:** Primary delivery target for scheduled jobs
|
||||
|
||||
## Discord
|
||||
@@ -45,8 +45,15 @@ sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
- **Home Assistant:** homeassistant-platform enabled
|
||||
|
||||
## Known Issues
|
||||
- Telegram thread_id `34795` for `telegram:1793951355` not found — one cron job delivered without thread_id
|
||||
- **Telegram thread delivery failures on `telegram:1793951355` (2026-09-30):** jobs `fad5a86979d4` and `1b23c042e17d` report `configured thread_id 34795 … was not found`, and `c8d52904e1d6` reports `Message thread not found` (`last_status: delivery_failed`). Content generation succeeds — only the thread target is wrong. Fix: recreate the topic, or clear `thread_id` on those jobs. See [[systems/scheduled-tasks]].
|
||||
|
||||
## Multi-bot group chat (open question, raised 2026-09-30)
|
||||
Anthony asked whether his other Hermes instances (the estate VMs/CTs) could share a group chat.
|
||||
- **Preferred shape:** a Telegram supergroup with **one forum topic per bot**, so each agent posts into its own thread and no two bots share a message stream. Mattermost was floated and rejected.
|
||||
- **Estate reachability:** CT460's Hermes serves the WebUI/API on `:9119` (locally fronted by nginx on `:19119`). Whether the other estate hosts expose `:9119` still needs checking before any fan-out design.
|
||||
- **Status:** design question only — nothing has been deployed or changed.
|
||||
|
||||
## Related
|
||||
- [[messaging-integrations]]
|
||||
- [[scheduled-tasks]]
|
||||
- [[systems/hermes-agent]]
|
||||
- [[systems/scheduled-tasks]]
|
||||
- [[infrastructure/tailscale]]
|
||||
|
||||
Reference in New Issue
Block a user