50 lines
3.1 KiB
Markdown
50 lines
3.1 KiB
Markdown
---
|
|
title: Hermes vs Nanobot
|
|
type: comparison
|
|
status: active
|
|
created: 2026-07-22
|
|
updated: 2026-10-20
|
|
verified_on: 2026-10-20
|
|
confidence: high
|
|
tags: [comparison, hermes, nanobot]
|
|
sources: [raw/configs/hermes-config-sanitized.txt]
|
|
---
|
|
|
|
# Hermes vs Nanobot
|
|
|
|
## Purpose
|
|
Compare Hermes (this agent) with Nanobot, another agent process in the homelab, and correct a stale claim in [[systems/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.org` → `100.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.
|
|
|
|
> **Re-verified 2026-10-20 — the core claims on this page still hold.** The `clawtest` peer is
|
|
> still on Tailscale at **`100.122.189.81`** (`tailscale status` → `100.122.189.81 clawtest
|
|
> anthonymau@ linux -`) and `http://nanobot.martinwa.org` still answers (**301**). So the
|
|
> correction recorded above remains accurate 90 days on.
|
|
>
|
|
> **One caveat worth adding:** CT333 now runs **both** Nanobot *and* ZeroClaw (the latter verified
|
|
> live on 2026-10-20 — see [[agents/zeroclaw]]). The page's framing of CT333 as the Nanobot host
|
|
> is not wrong, but the host is no longer single-purpose. Note also that **CT333 is `zeroclaw` in
|
|
> the current Proxmox naming** — the wiki uses the older "clawtest" label for the same LXC.
|
|
|
|
## At a glance
|
|
| | Hermes (ct460) | Nanobot (ct333 "clawtest") |
|
|
|---|---|---|
|
|
| Status | Active, primary agent | Active, running (was previously assumed dormant) |
|
|
| Host | Dedicated LXC, `agent;ai;automation` tags | LXC tagged/named "clawtest" |
|
|
| Public exposure | `hermes.martinwa.org`, `hermes-desktop.martinwa.org` | `nanobot.martinwa.org`, `nano-ssh.martinwa.org` |
|
|
| Extra services | Stratos command centre, browser/VNC stack | WhatsApp bridge |
|
|
| Role today | Primary 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.
|
|
|
|
## Related
|
|
- [[systems/nanobot]] — needs its "Current state" section updated to reflect this finding
|
|
- [[systems/hermes-agent]]
|