This gateway page gives the Orange Pi a clean launch lane into the OpenClaw instance running on this desktop. The actual OpenClaw UI stays on the Windows host and is published over Tailscale HTTPS, so the Orange Pi page acts as status, diagnostics, and launch control rather than trying to embed a frame that the upstream UI blocks. After launch, expect the Windows-hosted sign-in form first and enter the desktop gateway password there. The Agent Chat panel below lets you send messages directly to the desktop agent session from this page — no browser Control UI required.
Loading launch URL…Use the launch button to open the Windows-hosted OpenClaw UI over the Tailscale HTTPS hostname. This keeps the Windows host private to the tailnet instead of exposing it directly to the public internet.
The desktop OpenClaw gateway keeps its own auth boundary. This Orange Pi page does not proxy or store the desktop gateway password; it only exposes the live tailnet route and confirms the service is reachable. Seeing the desktop sign-in form after launch is expected, and the password is entered only in the Windows-hosted Control UI.
The upstream desktop OpenClaw UI sends frame-blocking headers. Opening a separate tab is the correct path, and this page reports that requirement instead of implying the remote session itself is broken.
If the launch target goes red, first verify Tailscale Serve is still forwarding on the Windows host, then verify the local OpenClaw gateway is still listening on loopback port 18789.
Use the Agent Chat panel below to send a message to the desktop agent session directly from this page. The Orange Pi backend bridges the message via SSH and the OpenClaw CLI. Useful when the agent is stuck mid-task and needs context — no browser Control UI required. The panel shows the most recent history and blocks until the agent replies.