audit 2026-10-24: conduit page + memory-start-timeout incident; 10-09 storm resolved; window 169/0; frontmatter for 2 legacy incident pages
This commit is contained in:
@@ -0,0 +1,91 @@
|
||||
---
|
||||
title: Conduit
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-10-24
|
||||
updated: 2026-10-24
|
||||
verified_on: 2026-10-24
|
||||
review_after: 2026-11-07
|
||||
confidence: high
|
||||
tags: [conduit, plugin, phone, iphone, push, voice, memory]
|
||||
sources: [live-probe, plugin-tree, live-sqlite-conduit, live-log, session-20261023_182601]
|
||||
---
|
||||
|
||||
# Conduit
|
||||
|
||||
## Purpose
|
||||
Hermes on Anthony's phone. A dashboard plugin + iOS app pair that pushes cards, prompts,
|
||||
location and health data between the Hermes gateway and the iPhone, and lets a **voice call**
|
||||
be started from the phone where the agent can speak and listen (`conduit-voice` sessions).
|
||||
|
||||
Related: [[systems/mnemosyne]] (memory backend the voice session reads), [[systems/hermes-ui]]
|
||||
(the browser desktop), [[systems/push-notifications]] (the older `hermes-push` bridge).
|
||||
|
||||
## Where it lives
|
||||
- **Plugin tree:** `/home/hermes/.hermes/plugins/conduit_push`
|
||||
- **Version:** `0.64.0` (`manifest_version: 1`), git HEAD `eaa14be` — *“Pulse: mark follow-up cards
|
||||
done, by hand or after Do it (0.64.0) (#323)”*
|
||||
- **Upstream:** `https://github.com/kaishi00/hermes-conduit-notifier.git` (origin, fetch+push)
|
||||
- ⚠ **The working tree carries an uncommitted local patch** (`M dashboard/plugin_api.py`, the
|
||||
memory-timeout fix in [[incidents/2026-10-22-conduit-memory-start-timeout]]). A plugin update
|
||||
that resets the tree drops it.
|
||||
- **Skills shipped with the plugin** (4, under `plugins/conduit_push/skills/`): `calling-the-user`,
|
||||
`reading-health-data`, `using-calendar`, `using-location`.
|
||||
- **Data stores** (`~/.hermes/`): `conduit-health.sqlite3`, `conduit-location.sqlite3`,
|
||||
`conduit-phone.sqlite3`, plus JSON state — `conduit-push.json` (credential / gateway id /
|
||||
installation id / relay url / e2e — **no values recorded here**), `conduit-calls.json`,
|
||||
`conduit-settings.json`, `conduit-present.json`, `conduit-desktop-views.json`.
|
||||
|
||||
## Current state (verified 2026-10-24 00:1x AWST)
|
||||
- **Dashboard gateway:** listening on `0.0.0.0:9119`; process started **2026-10-23 18:54:43** (this
|
||||
start picked up the memory-timeout patch).
|
||||
- **Device:** one registered — **iPhone, app version `2.0.0`**, features
|
||||
`chat-cards`, `info-cards`, `live-cards`, `maps-navigate`, `media-cards`, `show-cards`
|
||||
(last seen 2026-10-23 19:02:16). No other device is registered.
|
||||
- **Call settings:** `enabled`, `when_asked`, `decides`, `alerts` all true; rate limits
|
||||
`min_gap_s 120` / `per_hour 6` / `per_day 20`; `avoid_unknown_place` false.
|
||||
- **Recent calls:** two call sessions closed cleanly on **2026-10-24 00:03:23** and
|
||||
**00:06:57** (both `outcome: done`, `conduit-calls.json` written 00:06:57) — the first
|
||||
evidence after the memory-timeout fix.
|
||||
- **Data volume:** `conduit-health.sqlite3` is **561.7 MB** (WAL 6.1 MB) holding
|
||||
**1,501,165 `events`** rows across **308 `buckets`** / **62 `windows`** for its single device;
|
||||
`conduit-location.sqlite3` 80 KB; `conduit-phone.sqlite3` 284 KB. **No retention or
|
||||
compaction has been observed** — the health store has grown from card/health ingestion alone
|
||||
and is worth watching against the CT460 disk budget.
|
||||
|
||||
## Memory integration
|
||||
The voice session (`conduit-voice`) reaches Mnemosyne through the plugin's own memory layer, not
|
||||
through Mnemosyne's `system_prompt_block()` — recall is wrapped in a per-request deadline
|
||||
(`MEMORY_TIMEOUT_S`, default **60 s** as of 2026-10-23, overridable with
|
||||
`CONDUIT_MEMORY_TIMEOUT_S`; it was a hard-coded **10 s** before that, which was too short for
|
||||
Mnemosyne's 10–45 s cold start). If the provider fails to start, the plugin logs a warning and
|
||||
proceeds without recall rather than abandoning the call.
|
||||
See [[incidents/2026-10-22-conduit-memory-start-timeout]] and [[systems/mnemosyne]].
|
||||
|
||||
## Maintenance commands
|
||||
```bash
|
||||
# what version is installed / is the tree patched?
|
||||
git -C ~/.hermes/plugins/conduit_push log --oneline -1 && \
|
||||
git -C ~/.hermes/plugins/conduit_push status --short
|
||||
|
||||
# is the gateway up, and since when?
|
||||
ss -tlnp | grep 9119
|
||||
|
||||
# did a voice call lose its memory context?
|
||||
grep -h "Conduit" ~/.hermes/logs/agent.log | grep -i "memory" | tail
|
||||
|
||||
# state files (no secrets in the wiki)
|
||||
ls -la ~/.hermes/conduit-*.json ~/.hermes/conduit-*.sqlite3
|
||||
```
|
||||
|
||||
## Open items
|
||||
- Commit or upstream the `plugin_api.py` timeout patch so a plugin update cannot revert it.
|
||||
- No retention policy on `conduit-health.sqlite3` (561.7 MB and growing).
|
||||
- The Mnemosyne cold start that motivated the patch is still slow (10–45 s); only the *budget*
|
||||
was raised. → [[systems/mnemosyne]]
|
||||
|
||||
## Related
|
||||
- [[incidents/2026-10-22-conduit-memory-start-timeout]]
|
||||
- [[systems/mnemosyne]]
|
||||
- [[systems/scheduled-tasks]]
|
||||
- [[current-state]]
|
||||
Reference in New Issue
Block a user