stocktake(2026-10-11): skills-index 346 skills/70 cats; freshness 62 stale/24 fresh/7 no-date; 5 live-drift corrections

Drift found and corrected against live sources (not guessed):
- OmniRoute: CT600 omniroute is RUNNING and serving :20128 (combo API live);
  CT601 omni is STOPPED with onboot=0 (peer offline 54d). Wiki had these inverted.
  Hermes custom:omni resolves to omniroute -> CT600, not CT601.
- Third OmniRoute node discovered: omniroute-1 at 100.78.63.20:20128, live (401),
  registered as custom provider omni-101 (5384 models, default smart-route,
  carries skills_hub/free-stack). Not in pct list; identity unconfirmed.
- Ignis: TWO live instances. CT460 ignis (:8080, vault wiki/agent-estate-wiki) and
  CT200 ignis-ignis-1 (image ignis-server:latest, host 8092, vault /opt/ignis/vaults).
  Both return HTTP 200. Page now distinguishes them.
- Tailscale: /agent-estate targets bare 127.0.0.1:8769 (was .../8769/agent-estate-role-dashboard.html);
  undocumented tailnet-only :9443 -> 127.0.0.1:5173 added; CT201 routes corrected
  (8085 targets + /steel 5173 + /steel-api 3000, replacing the wrong :8443 -> :8082 row).
- Proxmox: rebuilt from live pct list + qm list. Added CT475 agentzero and VM110 omarchy
  (both previously missing); 282 ubuntu-server-xfce corrected to stopped; dead rows removed.
  VM403 open-claw and VM401 hermes-old absent from qm list - flagged unconfirmed, not deleted.
- Nanobot: gateway nanobot-gateway (PID 2259048) alive on 8765/8766. It is NOT systemd
  nanobot.service/gateway.service (both return inactive - wrong unit names). Port 8900
  no longer listening; "Serve API" claim flagged unverified.
- Docker: old "runtime not available" was a CT460 socket artifact (root:docker srw-rw----,
  hermes not in group docker, no passwordless sudo in cron). Documented CT200 (~50 containers),
  CT333 (9 containers), CT460 via sudo.
- Mattermost CT255 confirmed stopped; matches Tailscale peer offline 21d.

Flagged, not investigated (no root cause):
- mycompose-db-1 on CT200 is in Restarting (1) - crash-looping.

62 pages remain >21d stale and were NOT rewritten this pass (concepts, decisions,
comparisons, most runbooks) - not probed against a live source, so reported not faked.
Quartz rebuild step still inert (no quartz.config.ts) - public/ not refreshed.

Artifacts: systems/skills-index.md regenerated, raw/stocktake/freshness-20261011.txt.
This commit is contained in:
hermes
2026-10-11 03:11:07 +08:00
parent 7bffeab157
commit d981e30128
11 changed files with 318 additions and 70 deletions
+22 -8
View File
@@ -3,8 +3,8 @@ title: Nanobot
type: agent
status: active
created: 2026-07-22
updated: 2026-08-17
verified_on: 2026-08-17
updated: 2026-10-11
verified_on: 2026-10-11
confidence: high
tags: [agent, nanobot, homelab]
sources: [live-probe, runtime-config]
@@ -20,14 +20,28 @@ Primary homelab AI agent running on `clawtest` (CT333). Handles agent orchestrat
- **Workspace:** `/home/nano/.nanobot/workspace`
## Current state
- **Status: ACTIVE.** Confirmed running as of 2026-08-17.
- **Gateway:** port `8765` (HTTP API + chat completions)
- **WebSocket bridge:** port `8766`
- **Serve API:** port `8900` (host `0.0.0.0`, requires `api_key` in config)
- **WhatsApp Bridge:** `whatsapp-bridge.service` active on ct333
- **Model preset:** `freellmapi-auto` (current session); baseline context window 200,000 tokens
- **Status: ACTIVE.** Verified 2026-10-11: gateway process `nanobot-gateway` (PID 2259048) running and listening.
- **Gateway:** port `8765` (HTTP API + chat completions) — `LISTEN 0.0.0.0:8765`
- **WebSocket bridge:** port `8766` — `LISTEN 0.0.0.0:8766`
- **Serve API:** port `8900` was recorded as the Serve API; **not listening** in the 2026-10-11 `ss -ltn` check. Treat as unverified/possibly removed.
- **Service unit names:** earlier notes listed `whatsapp-bridge.service` — `systemctl is-active nanobot gateway` and `is-active gateway` are NOT valid here (both returned `inactive`). Nanobot runs as a user service under the `nanobot` user (`systemd --user`, PID 166) plus the `nanobot-gateway` process; it is **not** a system-level `nanobot.service`. Check the gateway port/process, not the systemd unit.
## Confirmed running on CT333 (2026-10-11)
| Process | Owner | Port(s) | Notes |
|---|---|---|---|
| `nanobot-gateway` (PID 2259048) | — | 8765, 8766 | The gateway |
| `mnemosyne` MCP (`mnemosyne mcp --transport std…`) | nano | — | `venvs/mnemosyne-mcp` venv |
| `chroma_query_api.py` | nano | — | started Sep 23 |
| `agentmail-daemon.py` | nano | — | started Sep 23 |
| `readlater` Next dev server | nano | 3210 | started Sep 23 |
Other listeners on CT333 include 8787, 8880, 8899, 8999, 3000, 5050, 8080 and the Tailscale 443.
## Docker on CT333 (verified 2026-10-11)
`steel-browser`, `gotify`, `readlater`, `readlater-extraction-worker`, `kokoro-tts`, `edge-tts`, `onecli-postgres-1`, `tender_brattain`, plus healthy `community-spark` and `quirky_darwin`.
## Cron jobs
Unverified against live Nanobot scheduler on 2026-10-11. Previously recorded:
- `auto-upgrade-freellmapi-safeguard` — daily at 03:30 AWST
- `morning-quota-report` — daily at 07:30 AWST
- `daily-quota-730am` — daily at 07:30 AWST