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: DOWN (as of 2026-08-07). Connection refused on port 8900 — the OmniRoute provider connection to nanobot (58debd59, prefix nanobot) was causing event-loop stalls because every model sync + credential health check retried it. Connection disabled in OmniRoute. Nanobot on CT333 is not responding.
Prior state: nanobot process listening on port 8766 (verified via ss -tlnp on ct333, 2026-07-22).
whatsapp-bridge.service (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status unknown as of 2026-08-07.
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

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.

Relevant runbooks

runbooks/restart-hermes

comparisons/hermes-vs-nanobot

3.3 KiB Raw Blame History