- 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
3.5 KiB
3.5 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Open-Claw | system | active | 2026-08-15 | 2026-11-11 | 2026-11-11 | high |
|
|
Open-Claw
Purpose
Autonomous AI agent gateway running on a separate QEMU VM. Docker-based with Tailscale networking, serving a control UI and gateway for AI agent operations. Completely separate from ZeroClaw despite the similar name.
Location
- VM: QEMU VM 403 (
open-claw) - Hostname:
open-claw - LAN IP:
192.168.178.193(DHCP) - Tailscale IP:
100.64.172.34 - Tailscale Domain:
open-claw.kangaroo-eel.ts.net - Control UI:
https://open-claw.kangaroo-eel.ts.net - OS User:
openclaw(sudo-capable)
Current State
- Status: NOT PRESENT. Live probe 2026-10-19: no VM 403 on PVE host 100.96.100.82 (
qm listshows only VMs 100, 101, 110, 282, 310;pct listshows CTs 103, 200, 201, 205, 207, 209, 215, 255, 270, 299, 333, 450, 460, 465, 475, 555, 600, 601). The VM was last known active on 2026-08-15. The content below documents the intended configuration and is stale/unverified until the VM is recreated or relocated. - Re-probed on the SECOND Proxmox host too, 2026-10-20. The
m93phost (100.104.51.98) has its own guest list — LXC 100obsidian-livesync, 101omniroute, 102vaultwarden, 104rclone, 105conduit, 221gitea, 245openweb, 500litellm, 1006freellmapi, 1007homebridge, 1008rustdesk, 1241ntfy, 1260freshrss, 1261paseo, 1262mailflow, 1263social-dashboard, 1264openmausbot, 998nightbridge(stopped) — and no VM 403 there either. The Tailscale peer list likewise contains noopen-clawnode. So Open-Claw is not merely moved between hosts: it is gone from both. - Guest lists re-probed 2026-11-11.
qm listonpve(100.96.100.82) now shows only VMs 100, 101, 110, 282 (VM 310 is gone too — the page previously listed it), andpct listshows CTs 103, 200, 201, 205, 207, 209 (stopped), 215, 255, 270, 299 (stopped), 333, 450, 460, 465, 475, 555 (stopped), 600 — CT 601 is gone as well. Live CT names read205 ollama,333 clawtest,450 hermesagent,600 omniroute. No VM 403 on either hypervisor, and noopen-clawTailscale peer — the "NOT PRESENT" verdict holds and is now ~3 weeks stable. - Consequence for the rest of this page: the Tailscale IP
100.64.172.34, the LAN IP192.168.178.193and the control UIhttps://open-claw.kangaroo-eel.ts.netare all historical. Treat the whole page as a design record, not a description of a running system. - Config format: JSON
- Auth: Password-based (not paired tokens)
- Software: Docker-based (community-scripts template)
Key Differences from ZeroClaw
| Aspect | Open-Claw (VM 403) | ZeroClaw (CT333) |
|---|---|---|
| Type | QEMU VM | LXC container |
| Config format | JSON | TOML |
| OS user | openclaw |
root |
| Auth | Password | Paired tokens |
| Tailscale | 100.64.172.34 |
100.122.189.81 |
Access
Via Tailscale:
ssh openclaw@open-claw.kangaroo-eel.ts.net
Via PVE:
sshpass -p 'admin' ssh -o StrictHostKeyChecking=no root@192.168.178.39 "qm guest cmd 403 exec-status"
Related
- agents/zeroclaw — Different daemon on CT333 (not the same!)
- agents/nanobot — Also on CT333 (different from both)
- infrastructure/proxmox — PVE host
- infrastructure/tailscale — VPN routing