- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13) - skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299) - runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated - comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest - incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised - incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused) - 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists) - log.md addendum + index.md date bump; no page deleted, no secrets written
56 lines
3.5 KiB
Markdown
56 lines
3.5 KiB
Markdown
---
|
|
title: Hermes vs Nanobot
|
|
type: comparison
|
|
status: active
|
|
created: 2026-07-22
|
|
updated: 2026-11-11
|
|
verified_on: 2026-11-11
|
|
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.
|
|
>
|
|
> **Correction 2026-11-11: the "CT333 is `zeroclaw` in Proxmox naming" claim was itself wrong.**
|
|
> Live `pct list` on the PVE host (`100.96.100.82`) still reports CT333's name as **`clawtest`**
|
|
> and `pct exec 333 -- hostname` returns **`clawtest`** too — the wiki's original label is correct
|
|
> on both counts. `zeroclaw` is only the **process/daemon** that runs inside CT333, alongside
|
|
> `nanobot`. Re-verified live the same day: the peer is on Tailscale at `100.122.189.81 clawtest`
|
|
> and `http://nanobot.martinwa.org` still answers **301**.
|
|
|
|
## 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]]
|