2.4 KiB
2.4 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hermes vs Nanobot | comparison | active | 2026-07-22 | 2026-07-22 | 2026-07-22 | high |
|
|
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, processnanobotlistening on port8766. - 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, andnano-ssh.martinwa.org→ SSH on the same host. - The earlier note "Nanobox on the PVE host at
192.168.178.39" conflated Nanobot withpve's own LAN IP (that address is Proxmox's web UI, per the tunnel'spve.martinwa.orgentry) — an error, not a second Nanobot instance.
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