Hermes vs Nanobot

Purpose

Compare Hermes (this agent) with Nanobot, another agent process in the homelab, and correct a stale claim in nanobot.

Correction to existing wiki content

systems/nanobot.md (written earlier the same day) states “No nanobot process running on this host” and “Unknown: whether nanobot should be redeployed on this host.” Both are superseded by direct verification during this pass:

  • Nanobot is running, just not on this host (ct460). It’s on LXC 333 (“clawtest”), Tailscale IP 100.122.189.81, process nanobot listening on port 8766.
  • ct333 also runs a whatsapp-bridge.service (“WhatsApp Bridge for Nanobot”) — a systemd service, active.
  • It’s publicly reachable via the same Cloudflare Tunnel that fronts Hermes: nanobot.martinwa.org100.122.189.81:8766, and nano-ssh.martinwa.org → SSH on the same host.
  • The earlier note “Nanobox on the PVE host at 192.168.178.39” conflated Nanobot with pve’s own LAN IP (that address is Proxmox’s web UI, per the tunnel’s pve.martinwa.org entry) — an error, not a second Nanobot instance.

At a glance

Hermes (ct460)Nanobot (ct333 “clawtest”)
StatusActive, primary agentActive, running (was previously assumed dormant)
HostDedicated LXC, agent;ai;automation tagsLXC tagged/named “clawtest”
Public exposurehermes.martinwa.org, hermes-desktop.martinwa.orgnanobot.martinwa.org, nano-ssh.martinwa.org
Extra servicesStratos command centre, browser/VNC stackWhatsApp bridge
Role todayPrimary personal agent (this wiki’s subject)Unclear — running, but purpose/overlap with Hermes not documented anywhere found

Verdict

Both agents are live simultaneously, which the wiki didn’t previously reflect. Worth a real decision: is Nanobot still needed alongside Hermes, or is it a leftover that should be retired (freeing ct333) or given an explicit distinct role? This comparison surfaces the question rather than answering it — no evidence either way was found on either host.

  • nanobot — needs its “Current state” section updated to reflect this finding
  • hermes-agent