Cold-Start OpenClaw v2026.5.2
Node 24, onboard, Port 18789 & Regions
This runbook assumes a fresh hosted Mac and OpenClaw v2026.5.2: install Node 24, finish onboard, supervise with launchd, then prove port 18789 before you declare victory. It ends with US East versus APAC plus when a budget SSD upgrade pays off. For rent-versus-buy and latency, read OpenClaw + Remote Mac in 2026: rent vs buy, latency, and SSH/VNC; for gateway placement basics, see OpenClaw AI Agent Gateway on a Remote Mac in 2026.
Node 24: two installation paths that both work
OpenClaw v2026.5.2 expects a current 24.x runtime so native add-ons stay compatible. Either isolate per user with a version manager or install one system-wide toolchain your plist can call—both are fine if you are explicit.
Path A (fnm or nvm): install for the service account, run fnm install 24, and put the absolute Node path in ProgramArguments. Path B (Homebrew or pkg): install node@24, point the plist at that binary, and verify with node -v from a non-interactive shell.
which node and node -v from the same user and environment file your launchd job uses; mismatched PATH values are the fastest way to ship a plist that silently runs the wrong interpreter after reboot.
onboard flow plus a launchd-shaped daemon
Run onboard interactively once so tokens, directories, and plugin hooks land where you expect, then move the steady-state process under launchd with KeepAlive, ThrottleInterval, and explicit log paths. Use a dedicated macOS user, load secrets from Keychain or root-owned env files the plist references, and reload the job after OS updates to catch missing libraries.
launchd working directories are easy to misread.
Port 18789 health checks in the right order
Confirm the job is loaded, confirm lsof -nP -iTCP:18789 -sTCP:LISTEN, curl localhost health, then test tunnels or VPN. Bind 127.0.0.1 when a tunnel fronts the port, and treat clock skew or missing TLS intermediates as infrastructure issues—not mystery application bugs—only after localhost is green.
US East vs APAC and cheap SSD: a decision matrix
Choose US East when identity, models, and CI controllers already sit in North America; choose APAC cities when measured RTT from your laptops wins. Gateways burn disk with traces and caches—add the smallest SSD tier that keeps plenty of free space after Xcode and snapshots.
| Signal | US East | APAC | SSD note |
|---|---|---|---|
| Median RTT to your laptops | Best for Americas-heavy teams | Best for Asia-heavy teams | Same rule: measure, do not assume |
| Upstream AI + SaaS endpoints | Often lowest hop count to US regions | May add trans-Pacific RTT | Large checkpoints punish tight disks equally |
| Ops window | Align with US business hours | Align with APAC business hours | Snapshot before upgrades either way |
| Budget SSD upgrade trigger | Free space < 25% for a week | Same threshold | Upgrade before latency spikes, not after |
- →US East: great default when GitHub Actions controllers and corporate VPNs already terminate nearby.
- →APAC: wins when your SSH sessions originate in Tokyo, Seoul, or Singapore and loss is low on your carrier.
- →SSD: sustained writes from agent logs matter more than synthetic read scores—buy headroom, not bragging rights.
Troubleshooting FAQ
node -v differ between SSH and the daemon?launchd does not. Put absolute paths in the plist or source a minimal env file from ProgramArguments before launching Node.ServerAliveInterval on SSH, corporate idle timeouts, and whether the tunnel maps the same interface you bound in the gateway config.Why Mac mini is the quiet layer under this stack
This workflow assumes macOS stays boring: Unix tooling without WSL drama, stable power, and weeks without driver roulette. Mac mini M4 delivers strong Apple Silicon throughput with idle draw far below most towers, which matters for always-on gateways. Gatekeeper, SIP, and optional FileVault shrink risk versus many Windows build boxes, and unified memory absorbs short agent bursts cleanly. If you want v2026.5.2 to feel production-grade, Mac mini M4 is the practical anchor—use the CTA when you are ready to match metal to the checklist.