2.9 KiB
2.9 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-10-20 | 2026-10-20 | 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. - 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