| name | hypha-status |
| description | Health check for the hypha daemon and archive. Reports whether the daemon is running, where the SQLite store lives, how many nodes are indexed, when the last ingest ran. Use when the user says "is hypha running", "hypha status", "hypha health", "/hypha-status". |
| argument-hint | null |
| allowed-tools | ["Bash"] |
/hypha-status
Verify that hypha is wired up correctly before running any of the other skills. Auto-starts the daemon if it isn't running.
Instructions
-
Run the ensure-daemon script:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/ensure-daemon.sh
-
Hit the daemon for a status snapshot:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/hypha-query.sh health
-
Report DB stats (no auth required for /v1/whoami):
curl -sf "http://127.0.0.1:${HYPHA_DAEMON_PORT:-3456}/v1/whoami"
-
Inspect the SQLite directly for indexed-node count + most recent ingest:
DB="${HYPHA_DB:-${HOME}/.hypha/store.sqlite}"
sqlite3 "$DB" "SELECT kind, COUNT(*) FROM records WHERE record_type='node' AND tx_invalidated IS NULL GROUP BY kind ORDER BY 2 DESC LIMIT 20" 2>/dev/null
sqlite3 "$DB" "SELECT MAX(ingested_at) FROM records WHERE adapter != ''" 2>/dev/null
-
Report:
- Daemon up/down + port
- DB path + total node count by kind
- Most recent ingest timestamp
- Whether passkey is paired (
/v1/whoami โ paired)
- Any obvious gaps (no calendar.event records โ user hasn't ingested calendar yet, etc.)
If the daemon is unreachable AND the binary is missing, tell the user how to build it (bun run build:binary from ~/Projects/hypha).
