--- title: Nanobot type: system status: degraded created: 2026-07-22 updated: 2026-10-12 verified_on: 2026-10-12 confidence: high tags: [system, nanobot, network] sources: [live-probe, omniroute-investigation] --- # Nanobot ## Purpose Role in Anthony's setup. ## Location - **Verified 2026-07-22:** LXC 333, hostname `clawtest`, Tailscale IP `100.122.189.81`. ## Current state - **Status: DEGRADED (re-verified 2026-10-12).** The Nanobot web UI on CT333 is **UP again**: HTTP `200` on `http://100.122.189.81:8766/` serving the nanobot web UI (verified this audit). However port `8900` — the endpoint the OmniRoute `nanobot` provider connection (`58debd59`, prefix `nanobot`) uses — is still **closed**, so the OmniRoute integration remains disabled. Contrast with 2026-08-07, when connection was refused on 8900 and no service was confirmed listening anywhere. - **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22); DOWN 2026-08-07 (connection refused on 8900 — OmniRoute event-loop stalls from model sync + credential health-check retries; provider connection disabled in OmniRoute). - `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status not re-verified on 2026-10-12 (SSH to CT333 not reachable from CT460: connection timed out on 22/tcp; verification above is TCP/HTTP probing only). - Publicly reachable via the same Cloudflare Tunnel as Hermes: `nanobot.martinwa.org` → `100.122.189.81:8766`, `nano-ssh.martinwa.org` → SSH on the same host. See [[infrastructure/domains-and-tunnels]]. ## Current state as of 2026-07-22 (superseded — see below) ~~- No nanobot process running on this host~~ ~~- `nanobot` systemd user service: inactive~~ ~~- Not present in `pgrep` process list~~ **Correction (this audit, same day):** the above was true only for *this* host (ct460) — Nanobot was never expected to run here. It **is** actively running, on LXC 333 ("clawtest"), confirmed via direct process/port check. Left the original lines struck through rather than deleted, per SCHEMA rule 9 (mark, don't silently delete). ## History - **User-provided:** Nanobox on the PVE host at `192.168.178.39` - **Correction:** `192.168.178.39` is `pve`'s own LAN IP (matches the Cloudflare Tunnel's `pve.martinwa.org` entry, which proxies to Proxmox's web UI on that address) — this was a conflation, not a second Nanobot instance. The real Nanobot host is ct333 (see Location above). - **Verified:** Lan/Wi-Fi node at `192.168.178.46` running ARM/arm64 firmware; `ubnt` login at `192.168.1.1` does not apply to this node - **Verified:** DWARF01 identified as a UniFi device; ONT01 status unresolved; DNS provided by `192.168.178.39`, not the router - **User-provided:** Avoid `heroku.com/archive` except for CAPI; use official CAPI course downloads instead - **Superseded:** "Nanobot may have been used previously as Hermes gateway or tunnel front on another host" / "Unknown: whether nanobot should be redeployed" — no longer applicable now that it's confirmed running; the open question is now *why* it's running alongside Hermes and whether that's intentional (see [[comparisons/hermes-vs-nanobot]]). ## Connected systems - [[systems/hermes-agent]] - [[systems/headless-server]] ## Known issues - Overlap/purpose vs. Hermes not documented anywhere — see [[comparisons/hermes-vs-nanobot]] for the open question this raises. ## Change history - 2026-07-22: audit corrected "not running" claim after direct verification on ct333. - 2026-08-07: status changed to DEGRADED — nanobot confirmed DOWN (connection refused on 8900). OmniRoute provider connection disabled. CT333 service status unknown. - 2026-10-12: web UI confirmed back up (HTTP 200 on `100.122.189.81:8766`, tailnet IP `100.122.189.81` = tailscale node `clawtest`). Status stays DEGRADED because the OmniRoute port 8900 endpoint is still closed. `whatsapp-bridge.service` not re-verified (SSH to CT333 unreachable from CT460). ## Relevant runbooks - [[runbooks/restart-hermes]] ## Related - [[comparisons/hermes-vs-nanobot]]