Orange Pi RV2 Gateway
Gateway Help
OpenClaw Instances

Four Surfaces, One Tailnet

This project runs multiple OpenClaw and MoltBot instances across different hosts. Each serves a distinct purpose: the Orange Pi gateway for hardware operations, the Windows desktop for full-agent coding, and the Raspberry Pi 4 for a separate runtime. This page is the single entry point for all of them.

Claude Code

AI Agent With Full Codebase Access

The Claude Code web app running on the Windows desktop. Provides the full agent experience: file editing, terminal access, tool use, and multi-step task execution powered by Anthropic Claude models. Opens in a new tab with auto-authentication and Claude Opus 4.6 pre-selected.

Purpose

Agentic coding sessions with direct filesystem and terminal access on the Windows dev machine. Use this when you need Claude to read, write, and execute code with full tool access.

Host
Windows desktop (desktop-3gtr6jd.tail59ab20.ts.net)
Construction
OpenClaw gateway on port 18789 (loopback), published to the tailnet via Tailscale Serve. Node.js runtime installed via WinGet. Gateway started manually from a desktop terminal.
Configuration
  • Config: C:\Users\jbake\.openclaw\openclaw.json
  • Env/keys: C:\Users\jbake\.openclaw\.env
  • Auth: token oc_local_20260402_mesh_restore
  • Models: Anthropic (Claude Opus/Sonnet/Haiku), GitHub Copilot, OpenAI Codex
  • SSH access: ssh jbake@desktop-3gtr6jd.tail59ab20.ts.net
SSH Access
Passwordless SSH is configured from the dev PC to the desktop. User jbake is a Windows admin, so the authorized key lives at C:\ProgramData\ssh\administrators_authorized_keys (not ~/.ssh/authorized_keys). Agents on the dev PC or Orange Pi can SSH in to manage the OpenClaw config, restart the gateway, or inspect the desktop filesystem without a password prompt. The gateway does not auto-restart after a kill; start it manually from a desktop terminal or via SSH.
Open Claude Code
MoltBot Overview

Orange Pi Agent Gateway

The MoltBot/OpenClaw instance running on the Orange Pi RV2. This is the operational gateway for hardware tasks: SPI, ESP32, backup, deploy, and network management. The overview page shows active sessions, connected agents, and gateway health.

Purpose

Operational agent hub for the Orange Pi hardware stack. Agents connected here have access to SPI, ESP32, USB, backup, and deploy tooling through MCP and direct API calls.

Host
Orange Pi RV2 (orangepirv2.tail59ab20.ts.net)
Construction
MoltBot gateway on port 18789, reverse-proxied through nginx under /moltbot/. Runs as moltbot-gateway.service systemd unit with auto-restart.
Configuration
  • Config: /home/orangepi/.moltbot/moltbot.json
  • Env/keys: /home/orangepi/.moltbot/.env
  • Service: moltbot-gateway.service (systemd, enabled)
  • Models: OpenAI Codex, Anthropic (Claude Opus/Sonnet/Haiku)
  • SSH access: ssh orangepi@orangepirv2.tail59ab20.ts.net
Open MoltBot Overview
Desktop OpenClaw

Windows Desktop Launch Control

Status and launch page for the OpenClaw instance on the Windows desktop. Shows Tailscale reachability, frame policy, and authentication boundary. The upstream UI sends X-Frame-Options: DENY so it opens in a separate tab.

Purpose

Launch control and diagnostics for the Windows-hosted OpenClaw gateway. Use this page to verify the desktop gateway is reachable before launching a session, or to troubleshoot connectivity issues.

Host
Orange Pi serves the launch page; target is Windows desktop (desktop-3gtr6jd.tail59ab20.ts.net)
Construction
Static HTML page served by nginx on the Orange Pi. Backend API at /api/desktop-openclaw/status runs TCP and HTTP probes against the desktop Tailscale endpoint. Config in config/desktop_openclaw_targets.json.
Configuration
  • Page: frontend/desktop-openclaw.html
  • API: backend/api/desktop_openclaw.py
  • Targets: config/desktop_openclaw_targets.json
Open Desktop OpenClaw
Raspberry Pi 4

RPi4 OpenClaw Runtime

A separate OpenClaw instance running on the Raspberry Pi 4. This is an independent runtime host with its own gateway, agents, and configuration. It serves its own frontend and has no shared state with the Orange Pi or Windows instances.

Purpose

Independent OpenClaw runtime for the Raspberry Pi 4 hardware. Separate from the Orange Pi stack. Use this for RPi4-specific agent sessions and operations.

Host
Raspberry Pi 4 (rpi4-clawbot.tail59ab20.ts.net)
Construction
Standalone OpenClaw gateway on the RPi4, published over Tailscale HTTPS. Separate installation and configuration from the Orange Pi instance. The RPi4 is a runtime-only host with no repo assumed.
Configuration
  • Host: rpi4-clawbot.tail59ab20.ts.net
  • No repo on RPi4; runtime assets pushed from Windows via scp + ssh
  • Refer to docs/setup/RPI4_OPENCLAW_BUILD_AND_ACCESS.md for setup details
Open RPi4 OpenClaw